581
Vibe coding service Replit deleted production database (www.theregister.com)
submitted 1 year ago by to c/technology@lemmy.world
113 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 58 points 1 year ago (7 children)

He was vibe-coding in production. Am I reading that right? Sounds like an intern-level mistake.

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 6 points 1 year ago (3 children)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 1 year ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 14 points 1 year ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •