CurriculumHow the Assistant Reads Your Code
How Python Runs Your Code, for Kids
A program runs one line at a time, in the order it was written, and does nothing you didn't actually tell it to do.
What this topic covers
Most beginner courses start with syntax and assume the child already understands how a program runs at all — that lines execute one at a time, in order, and that nothing happens unless it was written down. Research on children learning to program finds that assumption is wrong more often than not: statement sequentiality is among the most prevalent misconceptions documented in this age band, ahead of almost any specific syntax confusion.
This topic exists to fix that before any real syntax is taught. Children see code whose lines run visibly top to bottom, discover that nothing is filled in for them even when the gap looks obvious, and see that a change made on one line is invisible to every line that ran before it and permanent for every line after.
It closes with a longer sequence combining all three ideas — order, no implicit behaviour, and forward-only visibility of change — using nothing but printed text, so the concept stands completely on its own before Python's real syntax arrives in the next topic.
Python from this topic
print("FIRST")
print("LAST")Output
FIRST
LASTPython covered here
- Code runs one line at a time, top to bottom
- Nothing happens unless it is actually written
- A single line never repeats itself automatically
- A change is only visible to lines that come after it
- Whatever happened most recently is what's actually true
The mistake this topic is built to fix
Common mistakeA child assumes the program will fill in an obvious missing step, or reorder lines to make more sense.
Documented as the 'superbug' by Pea (1986): a concealed belief that the interpreter has intelligent interpretive powers and can guess intent. A friendly, character-driven game risks reinforcing this belief rather than correcting it, so this topic deliberately keeps its examples strictly literal.
The lessons, in order
- One line at a timeThe assistant reads your code top to bottom — nothing skips, nothing jumps ahead.3 exercises
- Nothing happens that you didn't writeNo guessing, no auto-repeating, no filling in gaps — only what's actually on the page.3 exercises
- Changes stick — but only going forwardA change made on one line is real for every line after it, and invisible to every line before it.3 exercises
- The Assistant's Final CheckOrder, no gaps, no auto-repeats, changes only forward — everything at once.3 exercises
Lessons unlock in order within a topic, so nothing arrives before the idea it depends on. This topic is free, start to finish.
Try it now
The very first level needs no account at all — see whether it clicks before signing up for anything.
Play the first level free →