this post was submitted on 24 Feb 2026
39 points (97.6% liked)

Programming

25780 readers
244 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I was handed a pile of vibe code. And you might be surprised to learn that it has a ton of bugs.

And tips on how to dissect it and break it up into something manageable?

you are viewing a single comment's thread
view the rest of the comments
[–] VibeSurgeon@piefed.social 5 points 1 day ago (1 children)

Handed to review, handed to maintain, handed to extend?

[–] reabsorbthelight@lemmy.world 1 points 1 day ago (1 children)
[–] VibeSurgeon@piefed.social 7 points 1 day ago

The same as taking over any legacy project applies, really.

Start out with some expectation management - the current state of the solution prevents progress from going fast, and your stakeholders need to understand that.

Then get some tests going, such that you can try to defend whatever value the system has, if any.

Finally, start refactoring as much as you can get the space to do. Repeat until the system reaches your desired state.