Skip to main content
Text ready — video coming soon

Stage 0 — Introduction to SDE

Welcome! You're at the very start, and I'm really glad you're here. You don't need to have written any code before. Stage 0 starts from zero.

If you've just read the Thesis and parts of it felt hard, that's fine: this stage is here to make it clear. If you came from the Welcome, you're in the right place too.

Stage 0 has two short courses. Take them in order:

Why this stage matters. The whole book rests on one idea: do what AI can't, and ask it to do what it can. In Stage 0, you'll see that idea at work, so that Stage 1 can build real skills on top of it. This is a first look, not mastery; Stages 1 and 2 build the real skill.

Why one example runs through the whole stage​

We follow one small example: a savings committee, like the ones many families and offices in Pakistan run. Every member pays the same amount each month, and each month one member takes all the money collected. The names and amounts in it are not real.

In Course 1, you'll read a short program that adds up what the members have paid. In Course 2, you'll read a program an AI wrote for the same job. It runs with no error. But the total it shows is not the one the organiser asked for. That leads to the big question of this stage: if AI can write code in seconds, what is my job? The rest of Course 2 answers it.

What you need, and what you don't​

You needYou don't need
A phone or a computer, and an internet connectionAny coding experience, or a degree
Time each day. The book asks for about four hours a day; in Stage 0, going slowly is fineMoney, an AI account or anything to install. Every example shows its result on the page

There is no test and no certificate. Each lesson ends with a few questions to answer from memory. You'll know Stage 0 worked when you read the Thesis again and it makes sense.

The one real risk, and how to stay safe​

The risk here is a pleasant one. The AI's program will work, and you'll be tempted to accept it without looking. Accepting AI's choices without checking them has a name in this book: vibe decisioning. Stage 0 shows you how easily it happens, and what to do instead.

Safety floor

Whatever the AI writes for you, it is not finished until you have checked it yourself. The AI can test its own work, but its tests can miss things, and it often sounds just as sure when it is wrong. And if something breaks later, "the AI wrote it" is not an answer anyone will accept. The work is yours.

Why the stage runs in this order​

Each step prepares the next. First, what software is, so that AI writing code feels like the next part of a story you know. Then reading a little Python, because you can't check what you can't read. Then the parts of an app, so you know where each rule lives. Only then does AI arrive, and you meet the big question ready to answer it.

Where to start​

Begin with the first course, Introduction to Software Engineering. Its first lesson starts with a sum you could do on paper.

Whenever you forget what a word means, the glossary has it.