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.

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.

You hire an astute, hard-working, fresh graduate to run things for you. You hand them the keys to everything in your company; that includes every system, every endpoint, every file, and every password, all of it. Your only instruction to them? "Go ahead and improve things!" Then, trusting in their competence, you leave them to it. Doesn't that sound like a recipe for disaster? Yet that's precisely what's happening in IT departments across the world.

How to track expenses for a business: categorize expense types (operating, software, cloud, travel, capital), choose a tracking method (spreadsheet, accounting software, expense management tool, or cost intelligence platform), connect data sources (bank feeds, cloud billing APIs, SaaS invoices), assign ownership per cost center, set a reporting schedule, and audit quarterly.