this post was submitted on 08 Nov 2026
105 points (96.5% liked)
Hacker News
5729 readers
568 users here now
NOTICE: The bot occasionally has downtime, sorry about that. I'm working on adding better monitoring and error recovery so I can get notified faster.
Posts from the RSS Feed of HackerNews.
The feed sometimes contains ads and posts that have been removed by the mod team at HN.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.