43
Tips on dissecting vibe code (lemmy.world)
submitted 1 month ago by reabsorbthelight@lemmy.world to c/programming@programming.dev
29 comments fedilink hide all child comments

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
[-] ChogChog@lemmy.world 10 points 1 month ago

“Working Effectively with Legacy Code” by Michael C. Feathers

In my opinion, we treat it the same as any spaghetti code

[-] ballmerpeaking@programming.dev 4 points 1 month ago

An absolute must have for any software engineer. Whether they think they work wirh "Legacy Code" or not.

this post was submitted on 24 Feb 2026
43 points (97.8% liked)

Programming

26276 readers
177 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
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev