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/
this post was submitted on 21 Jul 2025
19 points (100.0% liked)
Technology
39791 readers
276 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 3 years ago
MODERATORS
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.
If you didn't take prod down at least once in your career, are you even a developer?
I remember learning about operator precedence in SQL the hard way at 4pm on a Friday. I wasn't popular that day, and I never made that mistake again.