Before you build anything, you want the lay of the land: where to start, what you need, and what order to move in. This book runs in the exact sequence you build real software, each stage producing the one thing the next stage needs. Read it in order and you are never stuck starting a stage without what it takes to finish it.
The map: ten stages, one path
Every part of this book is one stage of a real software project, and every stage ends with something concrete in your hands:
- Plan: a spec your AI can build from.
- Dev Set Up: a machine and an AI agent ready to produce code.
- AI Set Up: the operating system you and your agents run everything from.
- Architect: a codebase layout your AI can extend without rewrites.
- Build: a real, running app.
- Debug: the skill to unstick your agent instead of abandoning the build.
- Harden: an app that is secure, tested, and ready for strangers.
- Ship: your software live on real infrastructure.
- Operate: a running system you can see into and keep healthy.
- Scale: growth without breaking, and knowing your limits.
Each stage's output is the next stage's input. That is the whole reason the order matters.
All you need: a computer and an agent
The book assumes a fresh machine, maybe a laptop you unboxed today. Everything else, the editor, the languages, the accounts, the hosting, gets set up exactly when you need it.
Two things before chapter one:
- A computer running Windows, macOS, or Linux.
- An AI coding agent. We help you pick one in Dev Set Up; until then, just read.
Your agent is your teacher, this book is your judgment. It tells you what to ask for, in what order, and how to know the answer is good.
Follow the stages in order
Go through the book in order on your first pass. Because each stage needs what the last one produced, jumping ahead means starting a stage empty-handed.
From the second visit on, use it like a manual: a deploy fails or a database buckles, go straight to that stage and skim.
Build as you read
This is not a read-only book. Every chapter ends with one concrete thing to do, and most hand you a ready-made prompt to paste straight to your agent, loaded with the judgment a senior engineer would bring but you could not write yourself yet.
That is why the web and ebook versions beat print here. You read on the same screen as your agent, copy each prompt straight across, and build as you go. A paper copy would leave you only reading, the one thing this book is not for.
So keep your agent open beside the book. Finish a chapter and your app has moved forward, not just your understanding.
Short by design, deep on demand
This book is deliberately short. AI changed how you learn: you no longer need a thousand pages spelling out every detail, because your AI can explain any part, in your own words, the moment you ask. So we kept only the signal, the judgment and the order that actually matter, and let your AI supply the depth on demand.
That is why there is no thick PDF to print. Learning is interactive now, so the book is built to be read beside your agent: hand it a whole chapter to go deeper, then ask your own follow-up questions until it clicks for you.
And because it lives on the page, it does what paper cannot: it tracks your progress, lets you leave notes where they matter, and copies any prompt or a full chapter in one click to feed your agent. You can also join the discussion on any chapter, and suggest edits to the content itself.
