At least it wasn't an AI agent that did it despite being told not to, repeatedly. And then refusing to restore from backups because they didn't exist.

showed it to senior folks who said the results looked fine

Did anyone look at the code?

Also, what's a "multi-type"? Does he mean he needed to check a different field? Or are they doing something unholy without real schemas and got burned because they're mess confused someone! Also, why is a junior being moved between teams and touching production immediately?

I have so many questions.

The second one makes a ton more sense, and is pretty hilarious.

And this is why there should always be a human in the loop for QA despite how many tests you have.

At least not as bad as that one that let some LLM to control the server then get pissed at it when it deleted the production database https://www.theregister.com/2025/07/21/replit_saastr_vibe_coding_incident/

First dev, seems like an honest mistake and not on them. They weren't properly informed of the schema, and seniors signed off before the script was run.

Second dev - it happens, but this is why backups are crucially important, and always test the code before running it on prod, even if it's a short script like this one.