this post was submitted on 24 Feb 2026
30 points (96.9% liked)

Programming

25759 readers
296 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
30
Tips on dissecting vibe code (lemmy.world)
submitted 18 hours ago by reabsorbthelight@lemmy.world to c/programming@programming.dev
23 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
[–] draco_aeneus@mander.xyz 1 points 2 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.