Operations | Monitoring | ITSM | DevOps | Cloud

Ask a software engineer what they do and the answer, for years, has been some version of "I write code." That assumption is unwinding fast. AI agents can now write code, review pull requests, run tests, and ship to production, and they're taking on a fast-growing share of that work. As agents absorb more of the execution, the human role shifts.

The conversation about AI and software development has mostly been about velocity. Developers write code faster. Pull requests ship sooner. Backlogs shrink. That part is real, and it matters. But there's a bigger shift happening underneath it, and most engineering leaders I talk to are only just starting to feel its weight. AI hasn't just made developers faster. It has fundamentally expanded who can create and ship software. That changes things in ways that velocity metrics don't capture.

When you’re building with AI, you can get a lot done in 30 seconds. Waiting minutes for CI feedback on your latest change can feel like an eternity. Chunk sidecars are designed to give you feedback fast, running your full test suite against the same Linux environment as CI, directly inside the agentic loop. Traditional CI pipelines can take five or ten minutes to catch a basic lint error or failing unit test.

AI adoption has accelerated faster than most organizations expected. What started with chatbots has quickly evolved into AI systems capable of making decisions across enterprise environments, with the promise of faster service and more efficient teams. But many organizations are discovering an unexpected challenge: as AI usage expands, costs become harder to predict. Most AI platforms operate on token-based pricing models.

AI has made writing code fast, and you can feel it. Commits are up, pull requests are up, new repos spin up over a weekend, and your engineers swear they are faster. But where are all the new products? If every team really got faster, the software you use every day should be getting visibly better. AI helped your engineers ship more code. It didn't help your team ship more products.

Platform engineering has become one of the most discussed topics in cloud native infrastructure. Yet despite the rising focus, most conversations around platform engineering skip over the uncomfortable truths. What actually works at scale? When should you build versus buy? And how do you avoid the traps that trip up even experienced teams?

Eight new Azure recommendation types now scan your environment for idle, unattached, and over-provisioned resources, then tell you exactly what to cut.