#continuous-integration

#continuous-integration

This is a state where we see that the teams that move fastest will be the ones with clear tests, tight review policies, automated enforcement and reliable merge paths. Those guardrails are what make AI useful. If your systems can automatically catch mistakes, enforce standards, and prove what changed and why, then you can safely let agents do the heavy lifting. If not, you're just accelerating risk,

Pair programming and continuous integration can go hand-in-hand. Pushing to main multiple times a day is hard in isolation, leading to delays, large PRs, and merge issues, Ola Hast and Asgaut Mjølne Söderbom mentioned in their talk about continuous delivery with pair programming at QCon London. Pairing enables instant code review, easier refactoring, fewer bugs, and higher team resilience. In an earlier article, Hast and Mjølne Söderbom mentioned that their team uses pair and mob programming with TDD;

This is a story of a memorable bug I encountered at work. As with every story of that kind, there are a few ways to look at it: it might save you some time if you encounter a similar issue; it surfaces the hidden work - work that is not visible when you only look at the output and artifacts; it demonstrates the benefits of broad knowledge.

Activision has slashed build times for COD: MWII in half, enhancing developer efficiency by identifying inefficiencies through MSVC Build Insights.

The pilot project enhances security for CNCF projects by isolating builds using microvMs, alleviating GitHub's concerns about self-hosted runners.