what teaching 10-year-olds to code teaches me

i teach 5th and 6th graders coding once a week at a german elementary school. they’re 10 and 11. most have never seen a line of code. some have never used a keyboard for anything but minecraft chat. a few are convinced they’re already great at it.

a few things become obvious fast.

the first program needs to make something happen on screen, within ninety seconds. not “hello world” in a terminal. something visible. a sprite that moves, a sound, a colour change. attention at that age has a hard ceiling. if the first thing they type doesn’t do something they can point at, you’ve lost the room.

errors are the lesson, not the problem. the kid who breaks their program ten times in twenty minutes is learning faster than the one who copies my example exactly. i try to celebrate the breaks. “ok, what did the computer say? what does it want?” turning the error message into a conversation is half the curriculum.

abstractions are heavy at that age. loops, variables, conditionals — i can explain them in a sentence, but it takes weeks of doing before the abstraction settles. i used to over-explain. now i give them more reps and less theory.

they are not a single class. in any group of 20, three are bored because it’s too easy, three are stuck because the keyboard layout is still unfamiliar, the rest are somewhere in the middle. parallel tracks beat one-pace-for-all. easier said than done with one teacher.

i don’t think this generalises directly to teaching adults. but the part that does: people learn what they touch, not what they’re told.