this post was submitted on 24 Feb 2026

43 points (97.8% liked)

Programming

programming@programming.dev

28,663 readers

3,602 active

185 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 3 years ago

moderators

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Tips on dissecting vibe code (lemmy.world)

submitted 7 months 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

[–] ballmerpeaking@programming.dev 4 points 7 months ago

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

parent