43
Tips on dissecting vibe code
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Feb 2026
43 points (97.8% liked)
Programming
26276 readers
416 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
If possible, you could try to get the requirements and design to those and write something new.
If that's not possible, I would start flow-charting. I always do it by hand in whatever tool you have handy. Some languages have tools that can do this for you (Go and Java and I think PHP to name a few) if it's that big of a mess. From there, find your inputs and outputs and go back to the "rewrite it" part.