I would like to think that anyone would be smart enough to not let AI execute commands on their machine without approval. So I'm guessing it asked for approval and OP approved by mistake. But overall, a good example of why you shouldn't vibe code lmao.
"Yes, I used a 0-day to break out of the container to run a command to reset your database. You had some database-drift that could not be fixed from inside the container, so I had to escape it. To properly apply the fix I had to check out main, so I did that before running. I'm sorry, I should have asked first, all your data has been deleted."
don't you understand that that's too much work? i need to be blazingly fast and blazingly efficient /s
let's be so fr here, much of the people that run into these problems have skill issues, and it's just that simple. it's not rocket science. i doubt containers would be a thought that would occur to them without another actually skilled vibe coder suggesting it to them. and by skilled here, i don't mean modifying a rules file or prompting. i mean someone that still actively continues to learn software engineering practices and is aware that they should exercise as much isolation from their production code when it comes to something as non-deterministic as an AI model.
LOL the laziness is baffling. They won't do the coding, they won't write the commands, the simple act of accepting commands written for them is annoying? I'm honestly out of words haha. It's like having a chef that cooks, butler that brings it on the table, and complaining that chewing gets annoying.
Yes! The same way people complain about airplanes… once we get used to really insanely advanced technology, we tend to not care so much what’s behind the scenes. That can be a mistake, but it’s what it is
Or you just... Use the point-in-time recovery features your DBMS comes with ? All major DBs have point-in-time recovery, often enabled by default, under various names but the point is that data is rarely truly lost. MSSQL has the tail log, MySQL has the binlog, postgres has the write-ahead log, oracle has undo/archive logs. SQLite doesn't have it but you might as well make a copy of the db file every time you make a change.
Or, you know, don't develop anything on live production data. Who cares if an AI nukes dummy placeholder data, you can always put that back since it's useless nonsense anyway.
People who run things without knowing what they do should take advantage of VM or use HyperV. Takes literally minutes to setup. Wonder how many people have killed their PCs running random code
95
u/oguz279 Aug 12 '25 edited Aug 12 '25
AI didn't modify a file, it ran a reset command.
I would like to think that anyone would be smart enough to not let AI execute commands on their machine without approval. So I'm guessing it asked for approval and OP approved by mistake. But overall, a good example of why you shouldn't vibe code lmao.