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

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

[–] 87Six@lemmy.zip 0 points 14 hours ago* (last edited 14 hours ago)

Unironically get Opus to get you a base of a flow document based on the code so you can figure it out.

Then of course, you dig in yourself, understanding what Opus said, then fiflling in the gaps.

Edit: I don't think you need to pay for Cursor to prompt Opus once for this. Just make sure to use Opus, Auto picks the dumbest model available on free tier.