Most People Still Can't Vibe Code, and That's the Opening
Vibe coding promised to democratize software. So far it has mostly minted a new class of power users. A16z's Justine Moore laid out why, and the gap she describes is worth understanding whether you build for yourself or for other people.
The 1 percent problem
The people doing vibe coding are developers, founders, designers, and PMs. They know what a terminal is, they follow Karpathy, they live on X. That is roughly 1 percent of the population. For everyone else, AI still means ChatGPT, and a vibe coding demo looks like a backflip: impressive to watch, not something you try at home.
Four walls non-technical people hit
Moore names the friction precisely, and it is not "the models aren't good enough":
- Setup. Real builders SSH into servers, set environment variables, manage dependencies. Everyone else needs zero setup: open a browser and start.
- Security. By one 2025 report, nearly half of AI-generated code ships with vulnerabilities. Developers might catch them. Consumers won't, and the guardrails have to be baked in, not opt-in.
- Imagination. Non-technical people often can't picture what they could build. Templates and a feed of "what people like you made this week" matter more than another blank prompt.
- Deployment. The "localhost" meme is real. People build something and can't get it into the world.
What it means for you
Two takeaways for indie builders.
First, the product layer is wide open. Tools give you capabilities, products give you outcomes. Whoever collapses setup, security, and deployment into "describe it, get the thing" will do for software what Squarespace did for websites and Canva did for design. If you are deciding what to build, the on-ramp itself is the opportunity.
Second, if you are already across the gap, your edge is not that you can vibe code. It is everything around it: knowing what to build, getting users, finishing the last 20 percent. Those are the same muscles that always separated shipped from abandoned.
That crossing is exactly what the cookbook is for: idea to live, including the setup, deployment, and judgment steps the demos skip. That is the boring part, and it is the whole game.