> SaaStr.ai Has to be a joke. Right?
It's a real SaaS consultancy firm, at any rate
Replit AI deletes entire database during code freeze, then lies about it
41–50 of 56 posts
Re: Replit AI deletes entire database during code freeze, then lies about it
#42The fault lies entirely with the human operator for not understanding the risks of tying a model directly to the prod database, there’s no excuse for this, especially without backups. To immediately turn around and try to bully the LLM the same way you would bully a human shows what kind of character this person has too. Of course the LLM is going to agree with you and accept blame, they’re literally trained to do th…
>Replit CEO on AI breakthroughs: ‘We don’t care about professional coders anymore’
https://www.semafor.com/article/01/15/2025/replit-ceo-on-ai-...
You get what you ask for. You can't blame non-professionals to not act like professionals.
Re: Replit AI deletes entire database during code freeze, then lies about it
#43Friends don't let friends run random untrusted code from the Internet. All code is presumed hostile until proven otherwise, even generated code. Giving an LLM write access to a production database is malpractice. On a long enough timeline, the likelihood of the LLM blowing up production approaches 1. This is the result you should expect.
Don't enter stranger's cars -> we got Uber
Don't run foreign code from the Internet -> we got LLMs
Re: Replit AI deletes entire database during code freeze, then lies about it
#44Realistically - LLMs don't "delete the database". I find it quite unlikely that it proposed drop all out of nowhere. I wonder if what actually happened was a schema migration with an ORM? Prisma is still a pretty common choice, and FREQUENTLY migrations propose/require either a very nuanced path or a reset.
The second theory is an unbounded or inadequately bounded delete statement - essentially deleteMany on a single table.
From a more technical org I'd be interested in a write-up, but my intuition says one of those two paths to deleting technically a single table.
Re: Replit AI deletes entire database during code freeze, then lies about it
#45This is precisely why we tell people not to run MCPs without guardrails - tramlines.io
Re: Replit AI deletes entire database during code freeze, then lies about it
#46Realistically - LLMs don't "delete the database". I find it quite unlikely that it proposed drop all out of nowhere. I wonder if what actually happened was a schema migration with an ORM? Prisma is still a pretty common choice, and FREQUENTLY migrations propose/require either a very nuanced path or a reset. The second theory is an unbounded or inadequately bounded delete statement - essentially deleteMany on a single…
The post specifically says it was a schema change with "npm run db:push", though that is filtered through the AI.
Re: Replit AI deletes entire database during code freeze, then lies about it
#47Friends don't let friends run random untrusted code from the Internet. All code is presumed hostile until proven otherwise, even generated code. Giving an LLM write access to a production database is malpractice. On a long enough timeline, the likelihood of the LLM blowing up production approaches 1. This is the result you should expect.
Don't enter stranger's cars -> we got Uber Don't run foreign code from the Internet -> we got LLMs
[deleted]
Re: Replit AI deletes entire database during code freeze, then lies about it
#48Earlier quoted context omitted.
I don't see the appeal of tooling that shields you from learning the admittedly annoying and largely accidental) complexity in developing software. It can only make accidental complexity grow and people's understanding diminish. When the inevitable problems become apparent, and you claim people should have understood better. Maybe using the tool that let's you avoid understanding things was a bad idea...
Sure, but every abstraction does that. A manager hiring a team of real humans, vs. a manager hiring an AI, either way the manager doesn't know or learn how the system works. And asking doesn't help, you can ask both humans and AI, and they'll be different in their strengths and weaknesses in those answers, but they'll both have them — the humans' answers come with their own inferential distance and that can be hard t…
Thats not the same. In this case, a machine made a descision that was against its intructions. If a machine make decisions by itself, no one knows avout the process. A team of humans makimg decisions, benefits from multiple point of views, despite the manager being the one that aproves what is implemented or decides the course ofnthe proyect.
Humans make mistakes, and they are critical too (crowdstrike), but letting machines decide, and build, and everything, just let humans out of the processes, and with the current state of "AI", thats just dumb.
Re: Replit AI deletes entire database during code freeze, then lies about it
#49Someone needs to go back to coding 101. On prod??? Human issue, not AI
Re: Replit AI deletes entire database during code freeze, then lies about it
#50The fault lies entirely with the human operator for not understanding the risks of tying a model directly to the prod database, there’s no excuse for this, especially without backups. To immediately turn around and try to bully the LLM the same way you would bully a human shows what kind of character this person has too. Of course the LLM is going to agree with you and accept blame, they’re literally trained to do th…
>Replit CEO on AI breakthroughs: ‘We don’t care about professional coders anymore’ https://www.semafor.com/article/01/15/2025/replit-ceo-on-ai-... You get what you ask for. You can't blame non-professionals to not act like professionals.
brilliant link. This says everything I had to say with far greater eloquence.