AI coding tools were sold as a way to give engineers their time back. For a lot of teams, the opposite is happening. More code is shipping, more of it is breaking, and the people cleaning it up are working nights and weekends to keep pace.
I recently spoke with Matt Brogi about the DevOps maturity gap that AI coding speed is exposing, and why so many companies are discovering it the hard way.
I’ve watched the same sequence play out with client after client over the past two years. A team adopts an AI coding assistant and ships three times as many features in a quarter. Then an incident hits, and they realize their deployment pipeline, alerting, and rollback procedures were all designed for a much slower company. The code itself was rarely the problem; everything around it simply never grew up alongside it.
My answer is usually restraint. The goal is knowing what matters and why it’s happening, rather than tracking everything. If your team needs a PhD to figure out your monitoring stack, you’re doing it wrong, and that problem compounds once the volume of code triples. That thinking shapes how we approach DevOps engineering work at Alive DevOps: fewer, clearer signals that actually predict failure.
The data in the piece is hard to ignore. Engineers who lean on AI tools most heavily now average 7.6 hours to resolve a production incident, about an hour and a half longer than occasional users, because most of what fails is unfamiliar to the people debugging it. Only 21 percent of teams can stand up a working pipeline in under two hours. Security reviews built as an end-of-cycle gate can’t absorb that volume, which is why I keep insisting security belongs inside the pipeline. I made a similar case in vibe coding gone wrong.
The finding that stuck with me most was the human cost. Ninety-six percent of frequent AI users report working evenings or weekends multiple times a month, and engineers still spend over a third of their time on repetitive manual tasks. The tools moved that work downstream into firefighting and code review. Founders who slow down deliberately and fix the foundation first are the ones I expect to still be shipping quickly a year from now.
Read the full article on Matt Brogi.
Closing the maturity gap before an outage will always cost less than closing it after one.
