What is vibe coding?
Vibe coding is building software by describing what you want in ordinary language and letting an AI write the code, accepting most of what comes back rather than reading it line by line. It is a real shift in who can make software, and it comes with a real catch.
The origin
A word for something people were already doing.
Andrej Karpathy, a founding member of OpenAI and formerly head of AI at Tesla, coined the phrase in early 2025 to describe a way of working he had fallen into: talking to a model, accepting its changes, and barely looking at the code. He meant it as an observation, and for throwaway projects he meant it approvingly.
- The idea spread because the experience was instantly familiar to anyone who had tried it.
- It described a genuine change: for the first time, the bottleneck on making software was describing what you wanted, not knowing how to type it.
- It was always about a posture, not a tool. You can vibe code in any editor, and you can use the same tools with complete rigour.
- The word is now used loosely for any AI-assisted coding, which muddies a distinction worth keeping: whether anyone read and understood what shipped.
What actually happens
Four steps, repeated until it looks right.
The loop is the same whether you are in a chat window, a code editor or a hosted app builder. Understanding it explains both why it feels magical and where it goes wrong.
- 01
You describe the outcome
"A booking page for a dog grooming business, with a form that emails me." The model infers everything you did not say: the layout, the fields, the colours, the framework, how the email is sent.
- 02
It writes the whole thing
Not a snippet. Files, folders, configuration, dependencies. On a hosted builder it also deploys, so within a minute you have a working URL.
- 03
You look at the result, not the code
This is the defining step. You judge it by what you see in the browser and describe the next change in plain language. "Make the header smaller, move the form up, use our green."
- 04
You repeat until it looks right
Each round is fast, which is why it is addictive. It is also why problems compound: every round adds code nobody has read, on top of code nobody read last round.
What it is genuinely good at
Three things it does better than the old way.
It is worth being precise about the upside, because it is large and it is not going away.
Starting
The blank page is gone. Getting from nothing to something that runs used to take a skilled person hours and an unskilled person weeks. It now takes minutes for either.
Exploring
When the cost of a version drops to nearly nothing, you can try five layouts instead of arguing about one. Being able to see the options is worth more than being right first time.
Unblocking
Most software that never got built died on a boring obstacle: a format nobody could parse, an integration nobody had time to read the docs for. Those obstacles are now minutes long.
The vocabulary
The words you will meet.
Enough to follow a conversation about it without nodding along.
Prompt and context
The prompt is what you ask for. The context is everything the model can see while answering: your files, your existing code, the error you pasted. Most bad output is a context problem, not an intelligence problem.
Agent
A model allowed to act rather than only answer: read your files, write changes, run commands, read the result and try again. This is what separates today's tools from a chat window you copy out of.
Hallucination
Confidently wrong output. In code it usually looks like a function or a library that does not exist, or one that exists but does not behave as claimed. It runs into the compiler or the test suite, which is why both matter more, not less.
Technical debt
Work you have deferred. Ordinary in software and manageable when someone knows it is there. Vibe coding produces it faster than any method yet invented, and invisibly, because no one read what was written.
FAQ
Questions people ask about this
Who invented the term vibe coding?
Andrej Karpathy, a founding member of OpenAI and formerly director of AI at Tesla, used it in early 2025 to describe letting an AI write code while you respond to results rather than reading the code. He was describing his own habit on casual projects. The phrase spread quickly because it named an experience many people had just had for the first time.
Is vibe coding the same as AI-assisted coding?
No, though the words are often used interchangeably. AI-assisted coding covers any use of AI while programming, including a senior developer who reads and rewrites every suggestion. Vibe coding specifically means not reading closely and judging the result by whether it appears to work. The tools are identical; the difference is how much human understanding is in the loop.
Do you need to know how to code to vibe code?
No, and that is the point of it. You will get something working without knowing any programming. What you will not get is the ability to tell whether what you have is sound, to fix it when it breaks in a way the AI cannot see, or to judge whether a suggested change is safe. Knowing how to code stops being about typing and starts being about reviewing.
Is vibe coding safe?
It is safe in proportion to what the code touches. A personal tool that formats your own spreadsheets can hardly hurt anyone. Code that handles customer data, takes payments or runs a business's public presence carries real risk, and the risk is specifically that AI output looks correct when it is not. The safety comes from review, testing and someone who is accountable, not from the AI.
What is the difference between vibe coding and no-code?
No-code tools like Webflow or Squarespace give you a visual editor over a system someone else built and maintains: you are limited to what it offers, but what it offers works. Vibe coding generates actual code, so there is no ceiling on what you can ask for, and no floor under the quality either. No-code constrains you into safety; vibe coding gives you freedom and hands you the risk.
Start your brief
Start your brief
Tell us what you're launching and what it needs to do. We reply within one business day with a fixed price and the first available Monday.
- Websites from $15,000 ex GST, fixed. The exact figure comes with the reply.
- A reply within one business day, from Michael, not a form robot.
- A thirty-minute call to hear what the site has to do.
- A fixed-price scope, sent as a web page with a version number.
- Kick-off on the next available Monday, held for you. We take four studio builds a month.