you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 1 day ago* (2 children)

In my company they're trying to make it so only non-dev/eng people can write code, so they can let all of us developers go. Managers already vibe-coded a replacement for our whole system in secret, and we only found out by accident. So at least Goldman Sachs is ahead of many in learning from their own idiocy.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 day ago (1 child)

    Before you go, you should helpfully vibe port and vibe refactor the original codebase to make it forwards-compatible with the new one.

    You should vibe code a backup version management system too, and give an agent control over it. Prompt it with an extensive and detailed list of all the ways it could lose the original data and tell it to be sure never to do any of them. Unless the data got corrupted somehow. How would we know if the data's corrupted? Running a suite of vibe-coded tests, of course.

    Practice your shocked face for when the agent does an oopsie and accidentally overwrites the only pre-slop versions.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 22 hours ago* (last edited 18 hours ago)

    It would have to wipe 15 years of source control, which would be impressive even for a "rogue" agent. Trust me, I've turned over a lot of ideas in my head during angry moments, but source control, backups and audit trails are sometimes there to protect us from our worse impulses.

  • source
  • parent