Before you open a single tool, there's something important to establish: your orientation.
You're not here to become a developer. You're here to become a Director: someone who holds the vision, makes the decisions, and guides AI with precision and intention. That distinction shapes everything that follows.
By the end of this lesson, you'll have one clear mental model in place: the macro/micro fractal. It's the organizing principle for this entire curriculum. Once you see it, you'll be able to place every subsequent lesson on it with confidence, and nothing you encounter will catch you completely off guard.
Here's the frame the whole curriculum hangs on. Before we name a single tool, get this picture in your head, because everything after it is just detail.
A film gets made by a small city. You have something stranger: a crew that never sleeps and does exactly what you tell it.
Creating something with AI is just like being the Director of a film. The goal is for every student to leave with a single, clear model they can apply to anything: every project moves through ideation, implementation, and review, and each of those phases contains the same three steps within it. Once that pattern is internalized, every lesson has a place to land.
Every film, every show, gets made by a small city. Writers, a camera crew, editors, a composer, a hundred people with valuable time and a budget that runs out. You don't have that. You have something stranger. A crew that never sleeps, works for pennies, and does exactly what you tell it. That's the power of AI.
Which leaves you the one job the crew can't do. You're the Director. You don't operate the camera. You decide what's in the frame.
You're the Director. You don't run the camera. You decide what's in the frame.
Every production, film or software, moves through the same three phases, always in the same order. In filmmaking, pre-production is where you figure out what you're making: the script, the plan, the shot list. Production is where you shoot it. Post-production is where you cut it together, finish it, and decide it's done.
Software works exactly the same way. The three phases just go by different names: ideation, implementation, and review. Ideation is where you figure out exactly what you want. Implementation is where you build it. Review is where you judge it and decide it's ready.
What does it mean to deploy? To deploy is to release the finished product to real people and put it live. You deploy the thing you built, not the plan you wrote. The spec is just the roadmap. Deploying is the finish line.
Here's the part that took me years to see. Each of those three phases is its own little production.
Pre-production has a pre, a production, and a post inside it. So does the shoot, and the shoot never goes to plan. The location isn't what you scouted, the light's going, a line isn't landing. So, you rewrite the scene right there, the AD reworks the day, you block the shot (figure out), you roll camera (build), you check the take on the monitor (judge), then you move to the next setup and do it again. This small loop runs all day, adapting the whole time.
It's the same shape at every size. The whole project is one big loop. Every piece inside it is a small loop of the same three. We call the big one macro and the small one micro. That's the entire framework.
The whole project is one big loop of three phases. Each phase opens into its own small loop of the same three.
It's the same shape at every size. That's the entire framework.
Here is the shape of the whole course: three macro phases, each mapped to the lessons that teach it.
After those five lessons, the course shifts to gear and judgment (the toolset you'll use, and the wisdom to know how to use it well). Lesson 7 introduces the core PairCoder workflow. Lesson 8 covers the advanced moves involved in working across multiple projects. Lesson 9 is about judgment, knowing which approach to reach for and when. Nine lessons, one shape.
Every lesson from here on tells you exactly where you're standing. Each one opens with a marker that names the current phase, macro ideation, figuring out what you want, so you always know which stage you're in. That orientation isn't just a label. Knowing which phase you're in is the whole game.
Here's the part nobody saw coming. Those three phases were never separate because the work demanded it. They were separate because moving between them used to cost a fortune. You locked the script before you rolled camera because changing your mind on set meant burning daylight and thousands of hours of labor. The budget forced the decision.
AI burns those walls down. You can change anything, anytime, for almost nothing. That sounds like pure upside, and in many ways it is. But those walls were also what made the Director decide. When nothing costs anything to change, nothing ever gets locked, and you spin forever.
So, the discipline the budget used to enforce is now on you. That is what this curriculum teaches. The framework isn't just a description of how good work flows. It's the structure you impose on yourself now that nothing external will.
The framework is the discipline you put on yourself now that nothing else will.
I built this site with this loop. The dashboard you're reading on, the curriculum around it, the booking flow, the billing, all of it. One person. The production phase practically drives itself now, it's a Ferrari. The engine is Claude Code, and the methodology that aims it is PairCoder. Point that engine with this methodology and you can build enterprise-grade software from a laptop, the kind that used to take that whole small city. But it only fires with all three: the tools, the methodology, and the one thing the crew can't fake, the spark of creation only a human brings.
Take yourself out of the loop, trust your first prompt, skip figuring out exactly what you want, and you get one of two endings. It doesn't work at all. Or worse, it holds together just long enough to fall apart the second you show it to a real person. That is the actual problem this solves. Building the Ferrari was never the hard part. Knowing where to point it is.
To be clear about what's what: the tools here aren't mine. Claude Code is made by Anthropic. PairCoder is made by BPS AI Software, and I'm a PairCoder affiliate. I teach with both because they're the best at what they do. What you're getting from me is the curriculum, a way to think and work. The tools are the ones I've found sharpest for the job.
Production, the actual shoot, is the most mechanical stretch of the whole thing. That's exactly why the machine takes it over first. Your value moves to the two ends. Knowing what's worth making, and knowing when it's right, especially when it doesn't feel right yet. That's the Director's job. It always was.
Now, you're the Director. It's time to start lesson 2, in pre-production, figuring out what you actually want. Welcome to the future, McFly.
Building the Ferrari was never the hard part. Knowing where to point it is.