Comment by dgellow

I would counter your counter :) I don't think vibe coding is about moving fast, shipping bugs, and not having reviews. That's the default state of pretty much all projects and is perfectly fine!

Vibe coding definitely has a different social meaning than just scrappy. I expect the term will die in some time as Claude Code equivalent becomes more popular, but right now I do find it pretty frustrating.

I do have a bunch of project prototypes done from scratch using Claude Code to explore ideas that I would qualify as vibe coded, but also some other projects that are done ~99% with Claude Code (I mean, the implementation, the design is mine), started as very scrappy prototypes, and evolved to something that is best in class in their specific somewhat niche domains (for things where I have expertise and feel confident I can judge). It's good software, reliable, strong focus on user experience, tested in prod, based on a few years of thinking what would actually fix once and for all a common issue in my niche at work. That's what makes me ask: at what point do you drop the vibe coded term?

It's not really about my personal perception of the project's value, more like... the idea that great software is rejected because it was written by an agent.

PS: congrats on sticking to your project for 5y, wishing you the best :)