Why do we have to call it vibe coding at all? Why do we have to invent what ends up being derogatory terminology and ultimately name-calling of well-intentional folks trying to do the best they can with an idea, regardless of their experience?
When the author of the software cannot confidently explain or does not understand the bugs the software has, performance issues, security vulnerabilities or clumsy architectural decisions.
This is before the obvious Claudisms, I immediately can see in a project README which is a sign that the author did not read their own README, and expects others to read it!
But similarly, you would want an experienced captain to fly a commercial plane with passengers from A to B safely over someone with no experience who vibe-coded a flight simulator for fun to take control of a real cockpit.
There is a clear expensive line between someone experienced and knows what they are doing with AI vs someone who does not and vibe codes want they do not understand with AI.
Why do we have to call it vibe coding at all? Why do we have to invent what ends up being derogatory terminology and ultimately name-calling of well-intentional folks trying to do the best they can with an idea, regardless of their experience?
When the author of the software cannot confidently explain or does not understand the bugs the software has, performance issues, security vulnerabilities or clumsy architectural decisions.
This is before the obvious Claudisms, I immediately can see in a project README which is a sign that the author did not read their own README, and expects others to read it!
But similarly, you would want an experienced captain to fly a commercial plane with passengers from A to B safely over someone with no experience who vibe-coded a flight simulator for fun to take control of a real cockpit.
There is a clear expensive line between someone experienced and knows what they are doing with AI vs someone who does not and vibe codes want they do not understand with AI.