what I always love about this stuff is most of the time it simply boils down to not committing changes. the LLM constantly assumes that you're committing, it will NEVER tell you or recommend you commit, but it assumes you are. so these tech bros are just cruising along, vibing, and then boom the agent does something that nukes the entire thing. panic. tech bro starts freaking out on the agent. agent says "lets rebase or pull the previous commit" and gives them the git code to do that. tech bro hasn't committed shit. and this is how you get a nuked prod environment.

[–] IphtashuFitz@lemmy.world 8 points 1 day ago (1 children)

None of that helps if you grant the LLM access to the production database and it decides to drop table user; to free up some space. That’s when you find out if your database recovery process actually works. You do have database backups, right? Or is that not a thing when vibe coding?

[–] valkyre09@lemmy.world 9 points 1 day ago

My friend and I set up Kopia in our home labs.

About a week later we decided to test out a disaster recovery only to discover we’d screwed up the permissions and nothing was backing up properly.

Was a relatively easy fix since we caught it, but I share this cautionary tale to remind you all to test your backups regularly!