DevOps / SRE / Platform · 27.08.2026, 19:47 UTC
AI Coded It, AI Shipped It, Who Owns It? by Ralph Bird
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | PagerDuty ↗ |
| Veröffentlicht | 27.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
We all know the tagline: it’s 03:47, and PagerDuty wakes you up again. Only now it is 2027, and it isn’t the same as it was in 2026, and it is astronomically different from how it was in 2020. The code that broke was written by an AI agent. It was shipped by another AI agent. No human read the diff because no human needed to; it passed every test, sailed through CI, and was promoted to production without a single raised eyebrow. It’s now 03:51. You’re awake and logged in. The SRE agent has tried to resolve the incident, but it couldn’t. It’s on you. What do you do? What should you have done to prepare for this moment? What do you need from the SRE agent now? This scenario isn’t science fiction. Pieces of it are already true today, and the rest is arriving faster than most engineering orgs are prepared to admit. The build side has already changed Coding agents writing and shipping production code isn’t a novelty anymore. It’s a normal Tuesday at a growing number of companies.1 The interesting part isn’t just that AI can write code now; it’s that the volume, speed, and quality of AI-authored changes are starting to outpace the human review processes that used to serve as the safety net. Consequently, we have to rely more on the AI to review the code. Will it be better? Will it be worse? Our prediction: AI review will be better on average and worse in the tail (even if it is coupled with a human review), and the tail is what pages you. The run side is next If coding agents are changing how software gets built, SRE agents will change how incidents get resolved. We’re already …