The tutorial lie

Somewhere in your first year of writing code, you followed a tutorial to the letter. You typed what they typed. It ran. And then someone asked you a question about it — why does the state go there? — and the answer wasn’t in you. You knew the incantation, not the spell.

That’s the tutorial lie. Not that tutorials deceive you on purpose — they don’t. They lie the way a tour guide lies: they show you the highlights and call it the city. The for-loop works. The deploy goes green. You feel capable. Then the first thing breaks — really breaks, nothing in the error message matches any line you wrote — and you discover the difference between having followed and having understood.

Anthropologists have a name for copying ritual without understanding meaning: cargo culting. Island airfield towers built of wood, hoping to summon the planes back. A useEffect with an empty dependency array, added because the video said so, hoping to summon the feature.

The test is simple and brutal: can you explain it out loud, to someone with no screen, in three sentences? Not recite it — explain it. If you can’t, you haven’t learned it. You’ve assembled it.

That test is the whole engine of this site. Every day ends with it. It’s slower than watching, slower than copying, and it’s the only thing that survives contact with a broken build at 11pm.