Chapter 0: Before You Start — What You’ll Build, How to Learn, and What to Do When You Get Stuck
Let’s Define the Scope Clearly First
The goal of Chapter 0 is simple: set expectations, define the boundaries, and lower the anxiety. After reading it, you should have two things in hand: a clear learning map and a unified “ask AI when you’re stuck” workflow. As for the full methodology behind Prompt / Context / Agentic, comprehensive overviews of AI tools, and systematic explanations of MCP / Skills, this chapter will not go into them, because they are not what you most need right now.
When many people open an AI tutorial, the most common problem is not “I don’t know how to use the tools,” but getting stuck on a string of questions first: I’m starting from zero, can I really begin; is this just another programming textbook in disguise; what exactly will I end up building; if I hit an error halfway through, will I be completely stuck.
Chapter 0 addresses these questions first.
After reading this chapter, you should at least be much more certain about two things: what this foundational series is actually teaching, and what your next step should be, instead of staying on the sidelines and hesitating.
Chapter Guide
| Section | What You’ll Get |
|---|---|
| 0.1 What this tutorial teaches, and what you’ll build | See both the positioning and the destination clearly |
| 0.2 Who this is for, and how to learn most effectively | Decide whether this path is right for you, and choose a learning route |
| 0.3 What to do when you get stuck: the unified support workflow for the foundational version | Get a standardized action template for asking AI for help |
| 0.4 Chapter summary: the foundational learning map | Wrap up Chapter 0 with a roadmap and move into Chapter 1 |
Remember This One Sentence First
This foundational series is not training you to “memorize knowledge like a programmer,” but to “build things like someone who creates real products.”
You will of course encounter some technical terms, such as prompts, Git, APIs, deployment, and environment variables.
But in the foundational series, the order in which these terms appear serves only one principle:
We explain them only when you actually need them, and only to the extent that lets you keep moving forward.
You will not be dragged into a pile of abstract concepts right at the beginning, nor will advanced system-engineering topics be forced on you before their time.
How to Read This More Smoothly
If what you most want to know right now is “is this something I should learn,” read 0.1 and 0.2 first. If what you fear most is getting stuck halfway through, start with 0.3. If you want a quick overview of the whole path, then read 0.4. Of course, you can also simply read in order from 0.1 through 0.4.
After Reading, You’re Ready to Go
If after reading this you already feel something like this—“Okay, I know this isn’t a syntax class; okay, I know what I’m ultimately going to build; okay, even if I get stuck, I know how to keep going”—then you can move on to Chapter 1 and start building the first real version.
Go to 0.1: What this tutorial teaches, and what you’ll build →