The guide
What is vibe coding?
Vibe coding is building software by describing what you want in plain English and letting an AI write the code. You steer the result through conversation — feedback, corrections, "no, more like this" — instead of typing syntax yourself.
The phrase comes from AI researcher Andrej Karpathy, who used it in early 2025 to describe a way of working where you "give in to the vibes" and judge the output by whether it does the thing, rather than by how the code is written. Since then it has become shorthand for the whole category of AI-assisted building.
I'm a 50-year-old with no technical background. I've used this approach to build nine real applications. Everything below is what I actually learned doing it, not a summary of other people's articles.
How does vibe coding actually work?
You open an AI builder, describe the app you want, and it generates a working version. You look at it, tell it what's wrong, and it revises. Repeat. The loop is describe → look → correct, and it runs dozens of times a day.
The skill isn't in the first prompt. It's in the correction. A vague "make it better" gets you noise; "the sign-up form should validate the email before it submits, and show the error under the field" gets you the thing you pictured. You end up learning to think like a product manager long before you learn anything about code.
What's the difference between vibe coding and no-code?
No-code tools hand you a fixed set of visual building blocks. Whatever the tool supports, you can build; whatever it doesn't, you can't. Vibe coding produces real source code in real frameworks, so the ceiling is much higher and the app is portable.
The trade-off is honest: real code breaks in real ways. Things go wrong that a drag-and-drop tool would never have let you do. That is the cost of not having a ceiling.
What can vibe coding not do for you?
This is the part most guides skip. The AI will build almost anything you describe. It will not tell you whether it's worth building, who would pay for it, or why the version you shipped last month got no users. I spent nine months learning that building is the easy half.
- — It won't choose your idea or validate demand.
- — It won't find or talk to your first customers.
- — It won't notice when a feature is technically fine and commercially pointless.
- — It won't stop you starting a tenth project instead of finishing the first.
How do you start vibe coding if you've never written code?
- 1. Pick something you understand. Build for a world you already know. Domain knowledge is the one advantage the AI can't hand you.
- 2. Start absurdly small. One screen that does one thing. My first prompt tried to build an entire platform and produced an unusable mess.
- 3. Describe outcomes, not implementations. Say what the user should experience; let the AI decide how.
- 4. Test everything yourself. "It generated without errors" is not "it works."
- 5. Run a security review before launch. Especially anything touching user data or payments.
- 6. Finish one thing. Nine half-built apps teach you less than one shipped one.
If you want the shortcut on step 3, I keep a library of 94 prompts that I actually used to build these apps — ten of them are free. And if you want the full walkthrough, read how to build an app with AI without knowing how to code.
Common questions about vibe coding
What is vibe coding?
Vibe coding is building software by describing what you want in plain English and letting an AI write the code. You steer the result by giving feedback in conversation instead of typing syntax. The term was popularised by AI researcher Andrej Karpathy in early 2025 to describe a workflow where you 'give in to the vibes' and focus on outcomes rather than lines of code.
Do you need to know how to code to vibe code?
No. You can build and ship a working app without writing code yourself. But you do need judgement: knowing what a good product looks like, describing problems clearly, testing what the AI gives you, and recognising when something is wrong. I had none of the coding and all of the judgement, and that turned out to be the half that mattered most.
Is vibe coding the same as no-code?
No. No-code tools like Webflow or Bubble give you a fixed set of visual building blocks. Vibe coding produces real source code in real frameworks — you're not limited to what a drag-and-drop editor supports, and you can take the code with you. The trade-off is that real code can break in real ways.
What can't vibe coding do?
It won't decide what to build, find your customers, or tell you whether an idea is worth the effort. It also struggles with anything requiring deep domain judgement, tricky security decisions, or large architectural changes late in a project. Those are still yours to own.
Is vibe coding safe for real, production apps?
It can be, with care. AI will happily write code that works and is still insecure — exposed data, missing access rules, secrets in the wrong place. Run a security review before you launch anything with user data or payments, and never assume 'it runs' means 'it's safe'.
How long does it take to build something real?
A rough working prototype can take an afternoon. Something you'd let a stranger use takes weeks. In my experience the first 80% is genuinely fast and the last 20% — the edge cases, the polish, the payments, the trust — takes as long as it always did.
How much does vibe coding cost?
Expect a monthly subscription for the AI builder plus small hosting and service costs. It is dramatically cheaper than hiring a developer, and dramatically more expensive than free. Budget for the months of iteration, not just the first build.
Am I too old to start vibe coding?
I started at 50 with zero technical background and have shipped nine apps. Age is not the barrier people assume; patience and clear thinking are the actual requirements, and both tend to improve with time rather than decline.
Where to go next
- Field Notes — the lessons, mistakes and mindset stuff, written after the fact.
- The projects — the nine apps, each with its own build diary.
- The full journal — everything, searchable.
- About the 50-year-old — who's writing this and why.
Newsletter · coming soon
Get the journal in your inbox
A weekly note on what I'm building, breaking, and learning. Drop your email and I'll send the first one when it launches.