A few years ago, if you wanted a custom tool for your business, you had two choices. Learn to code or pay someone who could.
Now there's a third option. You describe what you want in plain English, an AI writes the code, you run it, and you keep talking to it until it works. People call that vibe coding.
I've built websites for more than 15 years, mostly on WordPress. Then AI coding tools changed the speed and the math of custom builds so much that I wrote a whole post about it called I'm Done With WordPress. Today we're all in on Cursor for our sites, member tools, and content systems. So I have opinions on this one.
Here's what vibe coding actually is, what it's good for, where it goes wrong, and how to try it the smart way.
What is vibe coding?
Vibe coding is building software by telling an AI what you want in everyday language and letting it generate the code, instead of writing that code line by line yourself.
The term came from Andrej Karpathy, a well-known AI researcher, in an X post in early 2025. He described "a new kind of coding" where you "fully give in to the vibes" and "forget that the code even exists." He talked to his AI coding tool by voice, accepted every change without reading it, and pasted error messages back in until things worked. He also said it was "not too bad for throwaway weekend projects."
That last part matters. The original idea was playful. It was about fun, fast experiments where nobody gets hurt if the code is a mess.
The word caught on anyway. Collins Dictionary named vibe coding its Word of the Year for 2025, describing it as using AI, prompted by natural language, to write computer code.
Vibe coding vs. AI-assisted coding
This is the distinction most people miss, and it's the most useful thing in this post.
Developer Simon Willison wrote a great piece called Not all AI-assisted programming is vibe coding. His definition is simple. Vibe coding means building software with an AI without reviewing the code it writes. If the AI wrote it, but you reviewed it, tested it, and could explain how it works to someone else, he says that isn't vibe coding. That's just software development.
Google Cloud's explainer on vibe coding draws a similar line. It describes "pure" vibe coding, where you fully trust the output and move fast, and responsible AI-assisted development, where the AI acts like a pair programmer and you review, test, and own what ships.
So think of it as a dial, not a switch.
- Full vibes. You never look at the code. Great for a quick prototype, a personal toy, or testing an idea over a weekend.
- Guided vibes. You don't read every line, but you test everything, keep backups, and stop to understand anything that touches money, data, or logins.
- AI-assisted development. You use AI to write a lot of the code, and you or someone on your team reviews it before it goes live.
The mistake isn't vibe coding. The mistake is using full vibes on something that needs the other end of the dial.
How vibe coding works
The loop is the same no matter which tool you use. Google Cloud's page lays it out this way, and it matches how it feels in practice.
- Describe the goal. Tell the AI what you want in plain language.
- The AI writes the code. It creates or changes files for you.
- Run it and look. Open the page, click the button, try the thing.
- Give feedback. "That works, but the button is too small on my phone." Or paste the error message it threw.
- Repeat. Keep going until it does what you need.
That's it. You're not writing syntax. You're steering. That's why the skill that matters most is the same one that matters with any AI tool. Clear instructions. My guide on how to write AI prompts applies almost word for word here.
What vibe coding is good for
In my experience, it's at its best when the stakes are low and speed matters more than polish.
- Prototypes. Get an idea in front of real eyes before you spend real money on it.
- Internal tools. A simple calculator, a checklist app, or a dashboard only you and your team will use.
- One-page sites and landing pages. Quick pages to test an offer or an idea.
- Small fixes and tweaks. "Make the header sticky." "Add a contact form under the pricing section."
- Learning. Asking the AI to explain what it just wrote is one of the fastest ways I know to pick up how code works.
It's also a cure for a problem I know well. I once wrote about having about 10 half-built projects and almost none launched. Vibe coding makes it a lot cheaper to get from idea to something you can click. If you've been sitting on an idea, it's a good way to execute it before it becomes a project.
Where vibe coding goes wrong
The same speed that makes it fun makes it risky. Here's where people get burned.
Code nobody understands. Karpathy said it himself. The code grows beyond your comprehension. That's fine for a toy. It's a real problem when something breaks at 10 PM and nobody, including you, knows how it works.
Security holes. An AI can write code that works and still isn't safe. The OWASP Top 10 is the standard list of the most critical web application security risks, and it's worth a skim before anything with logins, forms, or payments goes live.
Leaked keys. Passwords and API keys pasted straight into code are a classic mistake. GitHub's secret scanning docs explain why. Credentials committed to a repository become targets for unauthorized access.
The endless fix loop. You paste an error, the AI fixes it and breaks something else, you paste that error, and an hour later you're further from working than when you started.
No backup. You let the AI make a big change, it goes sideways, and there's no clean version to go back to.
None of that means don't do it. It means set up a few guardrails first.
How to start vibe coding the smart way
Here's the approach I'd give a friend trying it for the first time.
1. Start with something small and low stakes
Pick a project where nothing bad happens if it breaks. A personal tool, a fun side page, or a prototype of an idea. Don't make your first vibe coding project the site that pays your bills.
2. Write down what you're building before you start
Type out a short plan. What the thing does, who it's for, what pages or screens it needs, and what "done" looks like. Paste that into the AI as your first message. A clear plan up front beats 50 fuzzy prompts later.
3. Ask for one change at a time
"Build me a whole app" is how you end up in the fix loop. Ask for one feature, test it, then ask for the next. Small steps are easy to check and easy to undo.
4. Back everything up before big changes
Use version control, like git, so you can roll back when a change goes wrong. Even if you never touch it any other way, treat it as insurance. That's exactly how I use it. I wrote about using git mostly as a backup and moving to Cursor Origin, and the idea is the same here. If the laptop dies or the AI goes rogue, the history shouldn't die with it.
5. Test it like a user, not like the builder
Click every button. Fill out every form. Open it on your phone. Try to break it. I put together a list of what to test before you launch a website or web app that works well as a checklist here.
6. Make the AI explain itself
When something important changes, ask "Explain what you just changed and why, in plain English." If the answer doesn't make sense, slow down. This one habit moves you from full vibes toward the safer end of the dial.
7. Keep secrets out of the code
Never paste real passwords, API keys, or customer data into the chat or into the code. Ask the AI how to keep keys in a separate settings file that doesn't get shared, and double-check it actually did that.
8. Get a second set of eyes before anything real goes live
If the project handles payments, personal information, or logins, have someone who knows code review it before launch. Vibe coding gets you to a working version fast. It doesn't replace a review when real people and real data are on the line.
Do you still need to learn to code?
You don't need to learn to code to start. That's the whole point.
But the more you build, the more a little knowledge pays off. You'll write better instructions, spot when the AI is going in circles, and catch problems earlier. Asking the AI to explain its own work is a painless way to learn as you go.
I see it the same way I see AI agents. I call my AI agent Punk, and the bots on that team do real work every day. But a person still decides what matters and approves anything that ships. If you want to go further down that road, read what is an AI agent and how to build an AI agent without coding.
Final thoughts
Vibe coding is real, it's useful, and it's not going away. It lowered the bar for turning an idea into something you can actually click on, and that's a big deal for anyone who's been waiting on a developer or a budget.
Just match the vibes to the stakes. Full vibes for weekend experiments. Backups, testing, and a real review for anything your business depends on.
What would you build if the code was the easy part?
FAQ
What is vibe coding in simple terms?
Vibe coding is building software by describing what you want to an AI in plain language and letting it write the code. You run the result, tell the AI what to fix, and repeat until it works, instead of writing the code yourself.
Who coined the term vibe coding?
AI researcher Andrej Karpathy coined it in an X post in early 2025. He described giving in to the vibes, accepting the AI's changes without reading them, and said it was not too bad for throwaway weekend projects. Collins Dictionary later named it its Word of the Year for 2025.
Is vibe coding the same as AI-assisted coding?
Not quite. Developer Simon Willison defines vibe coding as building with AI without reviewing the code. If you review, test, and understand the AI's code before it ships, that's AI-assisted software development. Google Cloud draws a similar line between pure vibe coding and responsible AI-assisted development.
Can you vibe code without knowing how to code?
Yes. You can build prototypes, simple tools, and basic pages by describing what you want. Learning a little along the way helps you write better instructions and spot problems, and asking the AI to explain its changes is an easy way to start.
Is vibe coding safe?
It's fine for low-stakes projects, but AI-written code can still have security holes or leaked passwords and keys. Back up your work, test everything, keep secrets out of the code, and have someone review anything that handles payments, personal data, or logins.
What should I build first with vibe coding?
Start with something small where nothing bad happens if it breaks, like a personal tool, a simple calculator, a checklist app, or a prototype of an idea. Build it one feature at a time and test each step.