• besselj@lemmy.ca
    link
    fedilink
    English
    arrow-up
    62
    arrow-down
    1
    ·
    2 days ago

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

    • Aatube@kbin.melroy.org
      link
      fedilink
      arrow-up
      44
      ·
      2 days ago

      he made the agent promise not to touch production data and was surprised when it did. it effectively ran a git push on the empty local testing database with upstream being production

    • Quibblekrust@thelemmy.club
      link
      fedilink
      English
      arrow-up
      19
      arrow-down
      4
      ·
      edit-2
      2 days ago

      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.

      • Gift_of_Gab (they/them)@lemmy.world
        link
        fedilink
        English
        arrow-up
        27
        ·
        2 days ago

        Replit is an agent that does stuff for you including deploying to production.

        Ahahahahahhahahahahhahahaha, these guys deserve a lost database for that, Jesus.

    • cyrano@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      2 days ago

      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