this post was submitted on 24 Feb 2026
37 points (97.4% liked)

Programming

25759 readers
301 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
37
Tips on dissecting vibe code (lemmy.world)
submitted 1 day ago by reabsorbthelight@lemmy.world to c/programming@programming.dev
28 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
[–] yaroto98@lemmy.world 19 points 1 day ago (2 children)

For work, or for hobby?

Hobby: have AI document what it's supposed to do, then work through it like the ship of theseus one function at a time replacing it with not bad code.

Work: use it, document the bugs, ninja in and clear them out one at a time until it works. Keep blinders on and ignore anything not directly related to each bug. Same strategy as legacy code.

[–] draco_aeneus@mander.xyz 3 points 9 hours ago

The problem with this approach is twofold.

  1. The AI doesn't know what anything is either. It can annotate faster than you, but if it is all wrong, that doesn't help.
  2. The primary reason the code is bad, and something the AI is particularly weak at without a human doing much of the thinking for it is architecture. Working your way through ship-of-theseus-style isn't going to address the fundamental reason the code is difficult to work with. The architecture.
[–] reabsorbthelight@lemmy.world 12 points 1 day ago (1 children)

For work. The code goes like 8 levels of abstraction. I'm trying to figure out how to unravel it.

Even a code flow/branching diagram would help I think

[–] zener_diode@feddit.org 6 points 1 day ago

Depending on the language, there might exist an automated tool for generating those kinds of diagrams from code.