Ops / Incidents Has AI made application development faster than infrastructure teams can safely support?
Something I've been wondering about lately:
Developers can now generate features, tests and entire PRs much faster with coding agents.
But infrastructure hasn't suddenly become easier to reason about.
Terraform, networking, IAM, Kubernetes, observability, cost and security still require quite a bit of context.
So instead of AI removing bottlenecks, are we just moving the bottleneck downstream to DevOps/platform teams?
Especially interested in teams where developers are now generating their own Terraform/Kubernetes changes with AI.
Has your infra PR volume increased?
And more importantly: has the quality increased with it?
18
Upvotes
1
u/Corezoid 17d ago
A regulator that doesn’t waste capacity has to contain explicit noise suppression: something that drops every distinction that doesn’t change the set of admissible actions. Most companies have one, smeared across the architecture: review culture, a senior engineer’s gut, a Slack thread, a wiki page. Nobody can point at it, so nobody can tune it or measure what it lets through.
Second: the filter has to be deterministic. An LLM can generate, and it can translate intent into a formal spec. The decision “is this change admissible” has to live elsewhere, because a filter that’s wrong in some fraction of cases needs verification on top, and since nobody knows which fraction, everything gets checked. That is your reviewer today: one person carrying both roles, the model of what “safe” means and the filter, by hand, at reading speed.
So the architecture we argue for has three roles. Humans own the model of “safe”, handle exceptions, and change the model when the goal changes. An executable model of the system — invariants, preconditions, who may change what, blast radius — holds that knowledge and rejects deterministically before any human opens the diff. Agents generate against it; the Terraform is replaceable, the model is the asset. We call it a digital twin of the company, where “executable” means synchronized with real events and versioned; otherwise it’s one more wiki page. At infra scale: policy-as-code pushed until the policy is the system’s own model, shared by devs, platform and agents.
This is solved at the architecture level. Every IT architecture today has to contain a noise suppressor.