Programming

25758 readers

216 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

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

Tips on dissecting vibe code (lemmy.world)

submitted 1 day ago by reabsorbthelight@lemmy.world to c/programming@programming.dev

24 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

[–] reabsorbthelight@lemmy.world 11 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 23 hours ago

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