Operations | Monitoring | ITSM | DevOps | Cloud

Sizing infrastructure has always required a balance between performance, capacity, and risk. What has changed is the level of precision required to make those decisions. Hardware timelines are less predictable. Costs are under closer review. Decisions that were once routine now require clear justification. In many cases, the question is no longer just how much capacity is needed, but whether that capacity can be delivered when it is needed and whether the investment will hold up under scrutiny.

A few months ago, Steve Yegge published his 8 levels of AI-assisted development, and it clicked the moment I read it, because I had lived that exact progression myself, moving from autocomplete to running agents one step at a time. Framed as an AI trust gradient, it finally gave the industry a vocabulary for something most of us were already going through without a name for it. If you haven’t read it, save it for later.

AI changed how code gets written before it changed how code gets operated. Generation accelerated; the downstream controls that turn that output into reliable, secure software at a reasonable cost did not keep pace. The result is elevated risk, distributed unevenly across engineering organizations. A recent survey explains why the distribution is so uneven.

This edition of the Pulse is shifting lanes. We’re calling it the AI Economics Pulse now, because the question on every finance leader’s mind is whether AI spend and the returns on it can be made to pair at all. That question came to a head over the last few weeks. The bills came due, and they came due in public. Uber burned through its entire 2026 AI budget in four months and capped employee spending on Claude Code and Cursor at $1,500 a month.

Your engineers run Claude Code. Your designers are in Cowork. Half the company has Claude open in a browser tab, and a few are on Cursor. It’s on their laptops, each person authenticated a different way, and none of it touches your gateway. The only record you get is one lump-sum bill at the end of the month. Now you can capture it where it happens – on the laptop.

Something unusual happened in the first half of 2026: the most productive AI coding tool on the market became the most financially dangerous. And the companies that discovered this the hard way read like a Fortune 50 roll call.

You’re scaling your IT infrastructure so you can do more — deploying across clouds and data center, adding servers, coding like crazy. Great! But how do you keep it all from falling apart? Policy as code is an approach to managing IT that strategically leverages infrastructure as code (IaC) and compliance as code to manage consistent policies across complex IT environments. Sounds perfect, right?

IPoDWDM is an architecture that integrates IP routing and Dense Wavelength Division Multiplexing into a single, converged platform. This integration is achieved by placing coherent optics directly into the ports of IP routers and switches, a fundamental shift from traditional network designs. Consequently, this approach eliminates the need for a separate, dedicated layer of optical transponders and their associated shelving.

Microsoft Copilot cannot see archived SharePoint content in either Microsoft 365 Archive or standard third-party archives. Here's why - and how to close the gap.