Agents will transform ops like Claude Code did engineering—only if ops first gets version control, tests, rollback
alex_verem · x · 2026-11-16
The author argues agents are about to do to operations what Claude Code did to engineering, but most ops teams lack the preconditions that made the engineering transformation work.
- Claude Code moved fast because repos already had history, tests, reviewers, and rollback—undoing a bad change was cheap.
- Most ops teams have none of that: a prompt buried in chat history isn't a system of record, and a payment to the wrong vendor doesn't fail a test—it hits the bank.
- Before putting agents on AP, claims, or support, ops needs a harness: the context the agent works from, allowed tools, checks on its work, and human takeover points.
Takeaway: version control, tests, review, rollback, and a named owner must come first.
More from coding & agent
- Dev open-sources discord-mcp: let Claude untangle Discord roles and permissions — PaSympaa · 2026-11-16
- Fable 5.2 vs Astra 6 on real PCB layout: 2 clean iterations vs 30 failed ones — ilovemydickuwu · 2026-11-16
- A six-step workflow for using AI to make open-source contributions — cneuralnetwork · 2026-11-16
- How Codex Happened: Inside OpenAI's comeback in coding, from a failed launch to swallowing ChatGPT — danshipper · 2026-11-16
- "When did you last build a dashboard by hand?" One quip nails AI's takeover of UI — tlakomy · 2026-11-16
- After 9 months, Forge open-sources a verification layer for AI coding agents — syrokomskyi · 2026-11-16