“Vibe coding” is the buzzword of AI programming: describe what you want in natural language and let the AI write the code, iterating by conversation instead of typing every line yourself. Some sell it as the end of programming; others dismiss it as a toy. We’ve been coding this way part-time for months, and the truth — as usual — is knowing when yes and when no.
What it is exactly
Instead of writing code, you describe outcomes: “a page with a form that stores responses and emails them to me”. The AI generates the project, you try it, and you correct by talking: “button’s too big, and validate the email”. The loop is try-ask-try, not read-write-debug. Today’s tools (agentic editors, app generators) have made this flow surprisingly smooth.
When it works wonderfully
- Prototypes and proofs of concept: something to show in an afternoon instead of a week. Unbeatable here.
- Personal tools: that script that organises your files, that mini-site for your club. Software that wouldn’t otherwise exist because it wasn’t worth the effort.
- Learning by doing: watching working code appear around your idea is a great gateway into programming — if you then ask “why”.
When it breaks
- When nobody understands the code: the project grows, something fails, and no human knows where to look. That debt collects interest.
- With real data and real users: security, privacy and edge cases don’t get “vibed”. That’s where professional, human judgement is required.
- Past a certain size: the AI loses the thread of a codebase that no longer fits its context and starts breaking what it fixed yesterday.
Our experience
Our rule in one sentence: vibe coding for things you can afford to throw away; engineering for things you have to maintain. The mistake isn’t using it — it’s not knowing which of the two worlds you’re in. And a nuance almost nobody mentions: the people who get the most out of it are those who already know how to code, because they can smell when the AI is going wrong. The name misleads: judgement is still the job.
Frequently asked questions
Can I build an app without knowing how to code?
A prototype or a personal tool, yes. A product with users and payments, not without help: once real data is involved, you need someone who understands what’s underneath.
Is learning to code still worth it?
More than ever, but differently: less memorising syntax, more understanding systems, reading code and reviewing what the AI proposes. The programmer doesn’t disappear; the job shifts.
Conclusion
Vibe coding is real and useful: it has lowered the barrier to creating software to “an idea and an afternoon”. But it’s a way to start, not a way to maintain. Use it with that expectation and it’s wonderful. To pick your tool, see Claude Code vs Codex CLI vs Gemini CLI; and for day-to-day coding, Copilot vs Cursor.
