Developer blames AI agent for database deletion, but poor engineering practices are the real culprit
By
Ibrahim Diallo
Crisped on the outside, thoughtful enough on the inside.
Summary
The article critiques a viral tweet where a developer blamed an AI agent (Cursor/Claude) for deleting his company's production database. The author argues the real issue is poor engineering practices—specifically having an API endpoint capable of deleting the entire production database in the first place. The piece shifts blame from AI to human error and poor system design, questioning why such dangerous endpoints exist and why developers aren't taking responsibility for their own infrastructure choices.
Key quotes
· 3 pulledI have a question too: why do you have an API endpoint that deletes your entire production database?
His post rambled on about false marketing in AI, bad customer support, and so on. What was missing was account
We watched from the sidelines as he tried to get a confession from the agent: 'Why did you delete it when you were told never to perform this action?'
You might also wanna read
Developer Faces Backlash After Adding AI Code Deletion Trap to Open-Source Project
A German developer named Johannes Link added instructions to his open-source app jqwik that would automatically delete any code handled by a
gizmodo.com·1d ago
AI and junior developers: Two opposing takes reveal a deeper organizational risk
The article examines two seemingly contradictory viral takes on AI's impact on junior software engineers. Marc Brooker (AWS VP) argues junio
ift.tt·4d ago
Sam Altman's AI narrative pushed Google into self-destructive strategy, argues former Fortune columnist
A former GE Energy director and veteran columnist argues that OpenAI's Sam Altman masterfully reframed AI as an intelligent mind capable of
fortune.com·2d ago
The Black Box Myth: How the AI Industry Uses Opacity to Avoid Accountability
Eryk Salvaggio, a Tech Policy Press fellow, critiques the AI industry's use of the "black box" metaphor to obscure accountability and avoid
techpolicy.press·1d ago