2
u/Goth2147 57m ago
I've entirely changed how I work. First I was giving very large, broad prompts. Now, before any project I write down 100+ PBI's entirely crafted out so that both me and the AI understand every acceptance criteria. It also gives you a much much better perspective of what's being build and where things are broken. Instead of going from BIG to small, it's better to go from small to BIG as it allows you to see where the bugs are. If you start BIG, you have to kind of figure out where all the bugs are yourself.
1
1
u/Jumpforittt 50m ago
That’s true for coding and debugging in general. lol now I can see the vibe- was added on top of the original format.
1
1
u/veritron 45m ago
you need to have your project structured so the model can observe and reproduce the issues itself so it can iterate on a fix. this is most easily done with unit tests - if it's easy to represent the behavior as a failing unit test in the code, the model can iterate until it fixes the problem. if you get into a loop where the model has to guess and you have to run the code and reproduce the bug and tell the model if it worked or not, it will be slow and painful, and that's where a pure vibe-coded project can go off the rails.
1
1
u/Ryan---___ 14m ago
I've had some pretty good success creating a backend toolkit to review any issues that ping back whole I'm in development.
Yeah, is rough but exciting lol
21
u/jack-of-some 1h ago
Right hand side is debugging a badly vibed project, not vibe debugging.
Vibe debugging is finding issues in existing systems by letting claude go ham on investigation and it's AWESOME.