Vibe Coding 101
You don't write code. You direct it. Think of yourself as a film director — you need to know what a good scene looks like, but you don't need to operate the camera yourself.
Vibe coding is being the restaurant owner who doesn't cook. You need to know what great food tastes like. You describe dishes clearly — "a creamy tomato soup, not too acidic, with fresh basil." And you need to send a plate back when it's wrong. But you don't need to know the difference between julienne and brunoise.
What Vibe Coding Actually Is
You describe what you want your software to do. AI writes the code. You review the result, give feedback, and direct the next iteration. Repeat until it's right.
You're a film director. You don't operate the camera, adjust the lighting, or act in the scenes. But you know what a good shot looks like. You tell the cinematographer exactly what you want — "tighter on the face, warmer light, slower pan." When the result isn't right, you recognize it and explain what to change.
The Minimum You Need
Three skills. None require a CS degree. All develop naturally.
Spot Obvious Problems
Like reading a recipe and catching "add 10 cups of salt." You don't need to understand every line — just notice when something seems off. Develops within weeks.
Understand File Structure
Your project is folders and files — like documents on your computer. "Login screen = this folder. Payment logic = that folder." If you can organize files, you can understand this.
Describe What You Want
The hardest skill — and it has nothing to do with technology. "Make the button your brand blue (#3B82F6), taller, rounded corners, with 'Get Started' in white." Precision = first-try results.
Vague vs. Precise
The difference between 5 rounds of "no, not like that" and landing it first try.
When AI Gets It Wrong
Confidently wrong ~15-20% of the time. Knowing the patterns saves you.
Invents Things That Don't Exist
"Just use the .autoResize() method" — except there is no autoResize method. It presents this with total confidence. If something sounds too convenient, verify it.
Adds Complexity, Not Fixes
When debugging, AI sometimes "fixes" symptoms with workaround layers instead of finding the actual cause. If a fix feels complicated for a simple problem, push back.
Contradicts Itself
In long conversations, AI recommends an approach then suggests the opposite later. This is why documentation (Ch 6) matters — your written decisions outlast conversational memory.
Assumes Your Project
AI might assume your database has a column that doesn't exist, or that you're using a tool you're not. Always verify its understanding matches your actual project.
After six months of directing, you understand your product more deeply than if you'd typed every line yourself — because you reviewed every line, questioned every decision, and directed every change.
The Learning Curve
Month 1 is hard. By month 6, you're building things you thought impossible.
You feel lost. Things break. You wonder if learning to code yourself would be faster. Push through.
You recognize patterns. You catch mistakes faster. Features that would've taken weeks now take hours.
You're building things you didn't think were possible for one person. The directing skill compounds.
Over time you develop a feel for when AI output is right and when something's off — the same way a director watches a take and just knows the actor is faking it. Trust that instinct. If code makes you uneasy, don't ship it.