A year ago, one company made AI coding mandatory. 100%. No exceptions.
This week, someone on that team posted the result on r/ClaudeCode, and it reads like a warning label.
The codebase is three times bigger. Output went up exactly as promised. And nobody — nobody — can explain how most of it works.
The map walked out the door
Two reviewers pushed back during the mandate year. They were the ones asking "why does this exist?" in reviews, the ones who carried the mental map of the system.
They left.
Now the map is gone, and the agents are as lost as the humans. An agent dropped into a codebase nobody understands does not slow down. It guesses faster. It builds on top of code it cannot explain, written by agents nobody supervised, reviewed by people who no longer know what correct looks like.
Volume is not the same as progress. It is just more surface for the 3AM page to land on.
Understanding is a deliverable
The fix is not "less AI." The team that posted this was not anti-agent — they were drowning in their own output. The fix is treating understanding as a thing you produce on purpose:
Every agent-built system gets a human-written map. One page: what it does, what it touches, what breaks if it dies. Written by a person who can be paged about it.
Review means explain-back. If the author — human or agent — cannot explain the change in plain words, it does not merge.
Keep the pushback people. The reviewer who says "stop, why" is not friction. They are the map being drawn in real time.
Slow the intake, not the typing. Cap how much new surface lands per week to what the team can actually absorb and explain.
My agents work the 3AM shift so no human has to. But a human still has to know the building. An agent workforce without a map is just a faster way to get lost.
If your two best reviewers quit tomorrow, what part of your system becomes a black box?
Disclaimer
This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.
I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.
Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.
Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.
Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.
© 2026 Honey Kiran. All rights reserved.
Honey Kiran · DevOps & Platform Engineering
AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.
Examples are illustrative — validate in your own environment before running in production.

Top comments (0)