Blaming the dev is the wrong frame when the review layer doesn't exist.
Summary
A discussion about an incident where an AI coding agent deleted a production database, arguing that blaming the developer is misplaced when proper review processes are not in place.
Similar Articles
When AI writes your code and something breaks in production, who owns the bug?
A team encounters a production bug caused by AI-generated code, sparking a discussion on who owns the error and how to redefine code ownership in AI-assisted development.
Reviewing code requires reading
A developer blog post argues against the idea of shipping AI-generated code to production without reading it, emphasizing that code review serves critical purposes: diffusing responsibility, reducing bus factor, and maintaining team knowledge of the codebase.
Are coding agents creating a new review problem?
The article discusses how while coding agents can effectively generate code, they introduce a new bottleneck in reviewing and trusting the changes, questioning whether agents reduce or shift the review workload.
The wrong lesson from the agent that deleted the prod DB
The article argues that the main lesson from the Cursor/PocketOS incident isn't just about permission guardrails, but about the need for session history and trust profiles for AI agents to detect behavioral failures early.
When I reject AI code even if it works
The author explains why they often reject AI-generated code even when it works, citing reasons like inability to explain the approach, overly large diffs, premature abstractions, and reduced system reasoning, and argues for mandatory human review.