So the question of “why does a public facing api that can delete your database even exit”?

If you worked in cloud environments - every database had public facing api that can delete it.

For the rest or it - yeah, running autonomous pipelines in production which decide what to run and what not to run seems fine until it isn’t.

But every database deployed in a cloud environment has an api that can delete it. Even if you say you’re running on vms - there exist api that can delete the disk, the vm, the network config, etc.

I think this goes to a broader point: developers aren't necessarily hired to write code.

They're hired to be responsible for some part of the product.

Introducing AI doesn't remove that responsibility.

Folks tend to focus on the code and the tools they're using (maybe I'm cynical from years in the industry). I don't think your boss wants to do your job, even if they could use AI to do it. I think your boss wants to have a headcount, and he wants the headcount to be responsible for the product.

Doesn't matter. He did it through the use of AI, and AI, despite explicitly told otherwise, deleted the database.

Both he should learned his lesson AND AI should not be trusted.

AI companies: here's a knife so you can automate bread cutting!

User: I tried to cut some bread and it cut my finger instead.

AI companies: not my problem!

HN: The AI didn't cut your finger, you did, idiot.

This has been covered elsewhere, but if you swear at Claude Anthropic will automatically bump you down into a lower quality model. It was found in the recent source code leak of Claude Code. So that's probably what happened to the guy who's Cursor deleted his entire production database.

It just goes to show, if you're a jerk, expect to be treated like one (even by an AI model)! Be polite, people.

I believe this is in response to PocketOS. When I read the original post, I was trying to figure out how they even built a workflow that had AI so close to the self-destruct button. This post's explanation about it probably being fully vibe-coded makes sense. How else would the system be so fragile and for the agent to have such far reach? They built a house of cards.

This applies to all infra.

Why can you delete a network load balancer that is still getting traffic?

Why can you delete a VM that is getting non-trivial network traffic?

Why can you delete a database that has sessions / requests in the last hour?

Why can you drop a table that has queries in the last hour?

Why do we even have that lever?

"Can't blame your tools" doesn't apply the same to software. I've never heard a coder say it either. Don't blame your compiler? Don't blame your os? These seem needlessly dogmatic