At what point is software considered "vibe-coded"?
We all use AI at some point when building software, but I don’t understand where the line is between AI-assisted development and vibe coding. What makes a project “vibe-coded”?
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.
Sadly, AI vibe coding is far worse. Following your manager's vibes, there was at least some semblance of accountability. Now when an AI vibe codes something, I'm not even sure whose ideas we're vibing on, or if they belong to anyone.
We would have to find another way to describe what you've just pointed out, which is, _very real_, and often exists in many large corporations and large "complex systems".
I'll call my phenomenon "management driven development" or MDD - a project that runs on hierarchical control, where management decisions are made on the hour and no one takes accountability.
False. If you don't know what your program is doing, and you're just 'trusting' the AI, you're vibecoding.