Vibe Coding Isn't a Myth — But Half Its Hype Is

Column Overview

Every year the tech industry mints a word that outruns its own definition, and in 2026 that word is vibe coding. Coined by former OpenAI co-founder Andrej Karpathy in February 2025, it describes a style of building software where you stop typing lines of code and start typing intent — you tell an AI system what you want, watch it generate and debug the implementation, and nudge it with more natural-language feedback until the result feels right. Collins Dictionary named it word of the year; Google search interest for the term reportedly spiked more than 6000%. The question worth asking a year and a half later isn't whether the phrase is catchy — it clearly is — but whether the thing it names solves a problem anyone actually had, or whether it's a narrative that got ahead of the product.

From autocomplete to autopilot

It helps to be precise about what's actually new here, because "AI-assisted coding" already existed before Karpathy's tweet. The older model kept the human in the driver's seat: a developer writes code, and a tool like GitHub Copilot fills in the next few lines or suggests a function body. Vibe coding flips who's driving. The AI produces the implementation end to end; the human's job shifts to describing what's wanted and judging whether the output actually works. The workflow becomes propose — observe — adjust, repeated in natural language, rather than write — compile — debug in a programming language. That's a meaningful shift in where human attention goes, and it's why the term caught on faster than "AI pair programming" ever did.

The case that the demand is real

Start with where the money went, because capital allocation is a decent proxy for whether investors believe in durable demand rather than a meme. Supabase, which provides backend infrastructure for AI-generated applications, raised $500 million in June 2026 at a $10.5 billion valuation — up from $2 billion just a year prior. More than 60% of new databases on the platform are reportedly created by AI tools, and annualized recurring revenue jumped from around $30 million to $70 million in roughly a year. Cognition AI, the company behind the autonomous coding agent Devin, closed a round exceeding $1 billion in the same window, pushing its valuation to $26 billion. Those aren't speculative seed checks; they're growth-stage bets on recurring revenue that's already showing up.

The usage data points the same direction. Market research pegs the vibe coding market at roughly $4.7 billion in 2026, with projections toward $12.3 billion — a 162% jump. Communities like r/vibecoding are reportedly growing membership at 16% a month, and about 80% of Fortune 500 companies are said to be using AI coding agents in some form. McKinsey's February 2026 study of 150 companies found routine coding tasks completed 46% faster on average, with code review cycles shortened by 35%; for boilerplate work like CRUD scaffolding, teams reported time savings as high as 81%. Cursor's own developer usage report shows the median developer's weekly coding volume more than doubling by May 2026 compared with a year earlier.

Then there's the access argument, which is arguably the strongest one. Y Combinator's Winter 2025 cohort survey found that a quarter of startups in the batch had codebases where up to 95% of the code was AI-generated. More strikingly, product managers, designers, and non-technical founders are shipping working prototypes — sometimes entire products — without ever hiring an engineer. That's not a marginal efficiency gain for people who already knew how to code; it's a door opening for people who didn't. Taken together, this is a reasonably compelling case that "turn an idea into working software without knowing how to program" is a real, previously unmet need, and one that's being met at scale right now.

The case that the hype outran the product

Set against that is a pile of evidence that the more ambitious version of the vibe coding story — that it can replace professional engineering outright — doesn't hold up yet. Practitioners describe much of what gets produced as disposable software: it passes the eyeball test, runs in a demo, and then turns out to be brittle, unverifiable, and expensive to maintain once anyone tries to extend it. That distinction matters, because "useful for a weekend project" and "worth paying to maintain for years" are different claims, and a lot of the current commentary conflates them.

The quality data backs up the skepticism. AI-generated code reportedly carries critical defects at 1.7 times the rate of human-written code, and cross-site scripting vulnerabilities at 2.74 times the rate. In one survey, 63% of vibe coding users said they now spend more time debugging than before they started using these tools — which, if accurate, undercuts the entire premise of net time savings. A security audit of 1,645 applications built on the Lovable platform found roughly 10% — 170 apps — carrying serious vulnerabilities including SQL injection, path traversal, and privilege escalation. A Stanford randomized controlled trial found something almost more troubling than the bugs themselves: developers using AI tools wrote less secure code but felt more confident about it, which is exactly the combination that lets vulnerabilities slip through review.

Trust data is trending the wrong way too. Stack Overflow's most recent survey found developer trust in AI-generated code falling from around 40% to 29% year over year, and the drop is sharpest among the most experienced engineers — only 2.6% of senior developers report high confidence in AI output. That's a meaningful signal, because senior engineers are usually the ones best positioned to catch subtle correctness and security issues, and they're the ones pulling back the hardest.

There are also early signs the market itself is cooling on the most aggressive version of the pitch. Barclays data shows traffic to Lovable, once valued at $6.6 billion, down 40% from its June peak. Inside Amazon, a push toward mandatory AI-assisted coding reportedly correlated with more production incidents, not fewer — output went up, but so did the failure rate. And there's a pattern several teams have independently described: excitement in week one, cracks showing by week three, the tool quietly abandoned within two months. The problem in these cases usually isn't that the AI can't write code — it's that the code it writes wasn't built with a multi-year maintenance horizon in mind, and the speed gains turn out to be borrowed against future technical debt.

Why "real need" and "real need at any scale" are different claims

The disagreement over whether vibe coding is a "fake need" mostly comes down to conflating two different questions: is there a genuine, previously unmet demand here, and can this specific approach satisfy that demand at every scale people are now claiming it can? Separating those clears up most of the confusion.

For prototyping, internal tools, MVPs, personal projects, and one-off ideas from people who aren't engineers, the demand is real and the tools are delivering against it — these are cases where "good enough and fast" was always the actual requirement, and it's now being met by people who previously had no path to it at all. For replacing an entire engineering organization or running a business-critical system that needs to survive years of maintenance, the evidence right now points the other way — this is closer to a narrative that ran ahead of what the underlying models and tooling can currently guarantee.

Put another way, the demand is layered, not monolithic. The base layer — turning an idea into something that runs — is a genuine need, and it's being satisfied. The top layer — the claim that this replaces professional software engineering as a discipline — is where a meaningful chunk of the current valuation and press narrative is standing on thinner ice than the numbers suggest.

Where this settles

Vibe coding isn't a fake need in any blanket sense, but its current valuation and media narrative have clearly outpaced what the underlying products can reliably deliver. A more honest way to sort the claims: rapid prototyping and MVP validation is a real need with demonstrated results; non-engineers building personal tools and small creative projects is a real need with a substantially lowered barrier to entry; boilerplate, CRUD, and standard-integration work is a real need with measurable efficiency gains; replacing a professional engineering team on production-grade, long-lived systems isn't supported by current evidence and looks more like an inflated narrative; and the "everyone's a programmer now" framing of total disruption is, at least in part, a story driven by capital and media cycles rather than by what's actually shipping reliably.

Karpathy himself has since talked about a shift from vibe coding toward what he calls "agentic engineering" — moving from a first wave built around speed and novelty toward a second wave that puts reliability, security, and maintainability back at the center. That transition is itself the tell. The market is correcting in real time, using exactly the evidence laid out above — security incidents, mounting technical debt, falling developer trust — to separate the durable need from the hype riding on top of it. The froth is being squeezed out; what's left underneath looks like it's here to stay.