Oh you made vibe coding work? Well then it's not vibe coding.
But any time someone mentions using AI without proof of success? Vibe coding sucks.
It's not vibe coding if you personally review all the diffs for correctness.
> According to Karpathy, vibe coding typically involves accepting AI-generated code without closely reviewing its internal structure, instead relying on results and follow-up prompts to guide changes.
What you are doing is by definition not vibe coding.
[dead]
No, what the other commenter described is narrowly scoped delegation to LLMs paired with manual review (which sounds dreadfully soul-sucking to me), not wholesale "write feature X, write the unit tests, and review the implementation for me". The latter is vibe-coding.