Day 01 — The Very Fast, Very Literal Apprentice

Ten minutes. One machine made of junk, one idea, one question. You will not install anything today.

One idea

A computer program is a set of instructions for an apprentice with two strange properties: it is unbelievably fast, and it is perfectly literal. It will do exactly what you said — millions of times a second — and never, ever what you meant.

Every bug in history is the gap between those two things. Programming is the practice of closing that gap, and it teaches you something no other subject does: how imprecise your own thinking was before something honest pushed back.

One more thing, because it’s 2026: machines now write code too. That doesn’t make this course obsolete — it makes it the whole point. When an AI writes the code, someone still has to say exactly what’s wanted and check that what came back is right. Direction and verification. That’s the skill this course grades, with the AI tools open on the table from day one.

Watch

Four minutes. This is a program — written in dominoes, paint cans, and pianos. One instruction triggers the next, exactly as built, no mercy for what the builders meant:

It took them months and dozens of failed takes. Every failure was a bug: the machine did what they built, not what they wanted. Watch it once for fun, then once as a debugger.

Carry the question

For the rest of today:

Pick one automated thing you touch — a doorbell, a playlist, a traffic light — and ask: what are its instructions, exactly?

Try to say them so literally that nothing is left to common sense. Notice how hard that is. No writing required.

That’s it. Day 1 is done.

If you’re still curious

Three doors. Open one, or none — they’ll be here tomorrow too.

See the family tree. Rube Goldberg machines — a century of intentionally absurd programs built out of physical stuff, long before software.

Hear the question carried in music. Put on Max Richter — On the Nature of Daylight and think about your one automated thing for its full length. Slow thinking about precise things is the actual job.

Ask someone. Ask someone who codes: “What’s the dumbest thing a computer ever did exactly because you told it to?” Every programmer has one. The story is always about the human.