Vibe coding gave non-coders a first prototype. Here’s the catch.
On February 2, 2025, Andrej Karpathy (formerly of Tesla and OpenAI) posted a single description of how he was writing software: “I just see things, say things, run things, and copy-paste things, and it mostly works.” That post got 4.5 million views. Within weeks, the New York Times and The Guardian had both covered it. The term he coined was vibe coding.
Stack Overflow’s 2025 developer survey found that 92% of U.S. developers now use AI coding tools daily. More pointedly, 37% said they’re vibe coding specifically, meaning the AI generates most or all of the code, not just autocomplete suggestions.
The market numbers
The vibe coding market is pegged at $4.7 billion in 2026, growing roughly 38% a year, and projected to reach $12.3 billion by 2027. Lovable, one of the larger AI app builders, reports that 63% of its users have never written code, and founders are its single largest user group.
The practical implication: the cost of testing a business idea dropped again. A founder with zero programming background can describe an app and have something in front of a real customer within days.
⚠️ What vibe coding can’t cover
The WEF’s Future of Jobs Report 2025 puts analytical thinking at the top of the skills employers want through 2030. Not a coding language. Not a specific tool. Analytical thinking.
That tracks with how vibe coding actually performs. An AI can generate a login page in ten seconds. It cannot tell you whether anyone will pay for the product, or whether three competitors already own that market.
The security picture is worth knowing before you ship anything real. OX Security found that 62% of AI-generated code ships with at least one baked-in vulnerability. GitGuardian’s State of Secrets Sprawl 2026 report found that AI-assisted commits leak hardcoded credentials at roughly double the rate of ordinary commits. Neither finding makes vibe coding reckless for a prototype. Both make it a problem the moment a product starts handling payments, logins, or personal data.
The operator takeaway
- Use a vibe-coded build to test whether anyone wants the product, not as the finished product.
- Get it in front of five actual potential customers before adding a single extra feature.
- Spend more time defining the problem than picking which tool to prompt.
- Before a product touches real payments or personal data, get a developer or security freelancer to review the code. Budget for that review as a real cost, not an afterthought.
Vibe coding makes the first version cheaper and faster to build. Everything the AI can’t do for you, knowing the customer, judging the output, and knowing when to call in someone who actually understands the code, still belongs to the founder.
I’m founder of BizStack at Cagri Sarigoz LLC and a passionate advocate for entrepreneurs.
With over 14 years in tech, marketing, and AI, including my role as Head of SEO at CitizenShipper and co-founder of TaleBot at Intale AI, I’m dedicated to sharing genuine, useful product insights and tips.
At BizStack, I aim to cut through the digital noise to provide clear, actionable advice.
And more than all else, I’m a father to a (always) little girl and a husband.
Contact me at [email protected] for assistance.
