The Portfolio Effect
Once you've built 3-5 things, something shifts. You stop seeing yourself as "learning to use AI" and start seeing yourself as "someone who builds things."
That shift is the point.
Layer Cake Development
Work, then polish, then delight.
Plan Before Code
Ask for a plan before implementation.
Each project teaches you something:
- Project 1: "I can build things"
- Project 2: "I can build things I want"
- Project 3: "I have a style"
- Project 4: "I can build things for other people"
- Project 5: "I can build things that ship"
The portfolio effect in action — real projects, real people
Prompt Archaeology
Visualized patterns from 10,497 prompts across 68 days of Claude Code usage. Data-driven self-reflection.
Learn Vibe Coding
This site. The curriculum you're reading right now was built entirely through vibe coding — a meta-example of the craft.
Don't rush it. But don't stop after one project, either.
Publish to CodeVibing
When you build something you're proud of, share it on CodeVibing — the community gallery for AI-generated components and projects.
Publishing does three things:
- It forces you to think about how your project looks to others
- It connects you with other vibe coders who can give feedback
- It builds a public record of what you've made
You don't need to be an expert. You just need to have built something.
Build Session
Build something real — something you chose because you want it, not because someone told you to. Stop reading and go build. This curriculum is useless without practice.
~45 min
Chapter 3 of 3