“Make me a website that tracks my running.” The AI writes it. You try it, ask for changes and never look at the code. That's vibe coding.
You hire a builder for a treehouse. You wave your arms: “Big, with a rope ladder and a little balcony.” They build it. You climb up and ask for a bigger window. They change it. You never once look at the plans.
That’s vibe coding. You describe what you want to an AI, it writes the code and you judge the result by trying it, not by reading the code. The name was coined by the AI researcher Andrej Karpathy in early 2025.
What it’s good for
- trying out an idea in an afternoon
- small personal tools and one-off scripts
- letting people who don't code build simple things
The risks
Nobody checked the code. It may have hidden bugs, security holes or messy shortcuts that make later changes painful. It can seem to work perfectly until it doesn’t.
What it isn’t
It isn’t the same as a developer using AI to help. Many professionals use AI to write code and then read and test it carefully. Vibe coding skips that step.
Where the comparison breaks down
A builder would warn you if the floor were unsafe. An AI usually won’t, unless you ask.
How the words fit together
Vibe coding relies on AI agents that write code. Without review, bugs and technical debt pile up unseen.
Vibe coding is great for quick experiments and personal tools. For anything handling money, passwords or customer data, someone should actually read the code.

When you'll hear it
“I just vibe-coded it.” I described it to an AI and used what it built, without writing the code myself.
“It's a vibe-coded prototype.” A quick version built mostly by AI, good for trying an idea, not yet for real customers.
“Who reviewed the code?” Has a person actually checked what the AI wrote?
“Who checks the code when part of this was built by describing it to an AI?”


