So... What Just Happened?
Module 1 · First Spark

So... What Just Happened?

The lecture, after the doing: what vibe coding actually is, and why describing something in plain English is enough to build it.

🔀 Now We Name It

You already built something. This lesson is the lecture — the part that usually comes first in a normal class — except now it’s explaining something you’ve already felt, not something abstract.

Vibe coding is building real, working software by describing it in plain language instead of writing code yourself. You describe the vibe — what it should do, how it should look, how it should feel — and an AI model writes the actual code behind the scenes.

That’s exactly what happened in the last lesson. “A soft blue about-me page with a random fun-fact button” is a vibe. You never touched the code that makes the button work. You directed; the AI built.


🎭 Two Roles, One Project

Every vibe coding session has exactly two roles in play:

RoleJob
You (the Director)Decide what should exist, describe it clearly, judge whether the result is right
The AI (the Builder)Translate your description into working code, instantly

Notice what’s not on the Director’s job list: knowing syntax, memorizing commands, understanding how the code is structured. None of that is required to direct well. What’s required is the same skill you already use to explain an idea to a friend — being clear about what you want and why.


⚙️ Why This Works Now (And Didn’t Before)

For most of computing history, “building software” and “writing code” were the same activity — you couldn’t do one without the other. That’s changed recently, and it’s worth understanding why, briefly:

AI language models got good enough at translating natural language into working code that the two activities split apart. You can now do the building software part (deciding what should exist, judging if it’s right) without doing the writing code part (typing exact syntax) yourself. The AI handles the translation.

This is genuinely new — not “always been possible but nobody told you.” It’s why this course exists now and not ten years ago.


🧾 A Few Words You’ll Keep Seeing

TermPlain-English meaning
PromptThe description you give the AI of what you want
Run / PreviewActually seeing your app work, not just reading about it
IterateAdjusting your description based on what you saw when you ran it
Deploy / ShipMaking your app reachable by other people, not just you

You’ll use “iterate” constantly starting next module — it’s the whole engine of vibe coding.

🧠 Knowledge Check

A friend says: 'I'd love to build an app, but I never learned to code.' Based on this lesson, what would you actually tell them?

Reveal Answer & Explanation

They don’t need to learn to code — they need to get good at describing what they want, clearly, to an AI that codes for them.

The skill that matters is being a clear Director, not a skilled Builder. That’s a communication skill, not a technical one — and it’s one your friend almost certainly already has.


⏭️ Up Next

Time to check what actually changed in your thinking — compare it to where you started this module.