What “vibe coding” actually means

A few years ago, building an app meant learning to write code — months or years of it. That's changed. Today you can describe what you want in plain English, and an AI writes the software for you. This is "vibe coding," and this course teaches you to do it well.

Where the term came from. The phrase was coined by Andrej Karpathy — a well-known AI researcher and founding member of OpenAI — in a post in early 2025 (February 2, 2025). He described a new way of building where you "fully give in to the vibes" and "forget that the code even exists": you talk to the AI, describe what you want, accept what it produces, and when something breaks you just paste the error back and let it fix it. The idea went viral because it captured something real — you can now build working software without writing (or even reading) the code yourself.

The honest definition — this is the most important idea in the whole course. The developer Simon Willison drew the line that experts now generally accept: vibe coding means building software with an AI without reviewing the code it produces. If you read the code, test it carefully, and can explain how it works, that's not vibe coding — that's just software development. You, as a non-developer, are doing literal vibe coding: you can't read the code, so you're trusting output you can't personally verify. That's completely legitimate for the right projects — but being honest that you're trusting unverified work is exactly why the limits and safety lessons later in this course matter so much.

How this differs from how professionals use AI. Professional developers also use AI heavily now (in tools like Cursor and GitHub Copilot), but they read and own every line — AI just makes them faster at something they could do by hand. You don't have that fallback. That's not a reason to avoid vibe coding; it's a reason to be deliberate about what you build with it. Vibe coding shines for prototypes, personal tools, and first versions. It's the wrong tool, on its own, for anything handling real money, identity, or sensitive data (Module 4 covers exactly where the line is).

What you judge instead of code. Since you can't read the code, you judge your app by results: does the preview do what I asked? Does clicking this button work? Is the layout right? Your skill as a vibe coder isn't syntax — it's describing clearly, testing carefully, and knowing what's safe to build.

The mindset: vibe coding means describing what you want and letting AI write the software — building without reading the code. The term comes from Andrej Karpathy (2025); the key distinction (from Simon Willison) is that reviewing the code makes it ordinary software development, while not reviewing it is true vibe coding — which is exactly what you'll do as a non-developer. That means you're trusting output you can't verify, so you judge by results (does it work?), and you match the tool to the job: great for prototypes and personal tools, risky for anything handling real data. Speed is the superpower; knowing the limits is the skill.