And this is why there should always be a human in the loop for QA despite how many tests you have.
Junior dev's code worked in tests, deleted data in prod
Submitted 8 months ago by eli001@lemmy.world to technology@lemmy.world
https://www.theregister.com/2025/07/14/who_me/?td=rt-4a
Comments
ZephyrXero@lemmy.world 8 months ago
PattyMcB@lemmy.world 8 months ago
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.
theherk@lemmy.world 8 months ago
They should have used all caps. Then it would have listened. Oh wait…
sugar_in_your_tea@sh.itjust.works 8 months ago
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.
SpiffyPotato@feddit.uk 8 months ago
The second one is a testament to why you should always run it as a
SELECTstatement first to verify you typed it correctly.