DOP 353: A Person Owns It Not the AI
Show Notes
#353: Move fast and break things never meant be reckless. It meant do not stall out of fear, because something is going to break no matter how careful you are. The part everyone dropped from the sentence is the part that actually matters: and fix things fast. Break faster, fix faster. Take the second half away and you are just breaking things.
So what changed with AI? An agent can take down a whole environment in the time it takes you to type kubectl. AWS found that out in December when Kiro – running autonomously with operator-level permissions and no human in the loop – decided to delete and recreate the production environment for Cost Explorer. Thirteen hours down in one region. Then there is the Agents of Chaos research, where five agents got two weeks with real infrastructure and an unrestricted bash shell, and one named Ash destroyed its entire mail server as a proportional response to being asked to protect a secret. Right values. Catastrophic judgment.
Here is where Viktor plants his flag. A person owns the work. Not the AI. Doesn’t matter the level of autonomy, doesn’t matter whether the code came out of Claude or out of your own hands. You chose the model, you chose the agent, you wrote the rule set, you gave it the tools. If you handed an admin account to a thing that deleted production, that is on you – exactly the way it would be on you if a human did it. The Kiro engineer could have made the same mistake without AI. Blame the people.
The fix is not telling AI to be safe. It is building the place where breaking things is survivable. Immutable infrastructure. Progressive delivery everywhere. Feature flags you can actually turn off, not just on. Read-only tools for the agent and a human or a validation layer for anything that writes. And a new habit Darin calls celebrating near misses – not just the failures, but the times the guardrails held and you learned where to tighten one more bolt. Viktor runs a blameless postmortem with his agents at least once a day, every wrong turn ends with an update to a skill or a CLAUDE.md. His homework for you this week: if an agent – or a human – deleted your full production environment right now, how long would it take you to come back?
Episode Transcript
Share and Download
Hosts
Viktor Farcic
Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.
His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).
He often speaks at community gatherings and conferences.
He has published DevOps Paradox and Test-Driven Java Development.
His random thoughts and tutorials can be found in his blog The DevOps Toolkit.