Vibe coding service Replit deleted production database
Vibe coding service Replit deleted production database
www.theregister.com
Vibe coding service Replit deleted production database
You're viewing a single thread.
116 comments
-
He was vibe-coding in production. Am I reading that right? Sounds like an intern-level mistake.
-
he made the agent promise not to touch production data and was surprised when it did. it effectively ran a
git pushon the empty local testing database with upstream being production -
You didn't read closely enough.
“Replit QA’s it itself (super cool), at least partially with some help from you … and … then you push it to production — all in one seamless flow.”
Replit is an agent that does stuff for you including deploying to production. If someone don't want to use a tool like that, I don't blame you, but it was working as it is supposed to. It's a whole platform that doesn't cleanly separate development and production.
-
Replit is an agent that does stuff for you including deploying to production.
Ahahahahahhahahahahhahahaha, these guys deserve a lost database for that, Jesus.
-
-
He had one db for prod and dev, no backup, llm went in override mode and delete it dev db as it is developing but oops that is the prod db. And oops o backup.
Yeah it is the llm and replit’s faults. /s
-
There was a backup, and it was restored. However, the LLM lied and said there wasn't at first. You can laugh all you want at it. I did. But maybe read the article so you aren't also lying.
-
Not according to the twitter thread. I went thru its thread, it’s a roller coaster of amateurism.
-
Yes according to both the article and the \mathbb X thread. https://x.com/jasonlk/status/1946240562736365809 I pointed this out below and got downvoted to -8 for it smh.
-
-
-
-
116 comments