The pitch is seductive: describe what you want to build in plain English, and an AI writes the code for you. No programming background required.
Wired put this to the test in a recent piece, documenting what happens when a self-described "normie" - no technical training - uses Claude to build a database for tracking petty complaints. The result: yes, it works. But with limits that matter for anyone thinking about trying it.
"Vibe coding" is the informal name for using a large language model (an AI trained on enormous amounts of text and code) to write software by describing what you want in plain language. You say "build me a form where users can submit complaints and I can filter by category." The AI generates the code. You don't write a single line yourself.
Where It Actually Works
Simple builds are genuinely achievable. A database with input fields, a display view, and basic filtering - Claude handles the structure, logic, and syntax without you touching a single bracket. The Wired experiment confirms what a lot of practitioners have quietly discovered: if you can describe what you want clearly, you can get something functional. A freelancer building a simple internal tracker or a content creator automating a narrow workflow now has a real path that wasn't viable two years ago.
The Debugging Wall
The honest limit shows up when something breaks. You're dependent on the AI to diagnose problems you can't read yourself. Debugging becomes a conversation where you describe symptoms without knowing the vocabulary - and that conversation gets slow and frustrating. Error messages mean nothing to you. Every fix is a guess relayed through natural language.
Scope is the other limit. Anything involving user authentication, persistent data storage across sessions, or deployment beyond a local browser tab gets complicated fast. The gap between "a prototype that runs on my machine" and "an actual usable product" is where most non-technical builders hit resistance.
Vibe coding has genuinely lowered the floor - small, specific tools are now within reach for non-programmers. But it hasn't eliminated the ceiling. Claude is an effective co-pilot for this kind of work. It's not yet a replacement for understanding what you're building when things go sideways.