CODING
ADVENTURE
0 / 12 completed

LEARN TOGETHER

A first step into Python.
A little help beside it.

A practical guide for parents, teachers and coding clubs supporting complete beginners aged 12+.

Can a complete beginner use Coding Adventure?

Yes. Start with the first activity, which introduces instructions, strings and variables. The learner can run real Python 3 in the browser, reveal hints and change a worked example. The full mystery is in the book; every companion activity is available without buying it.

What do we need?

Use a modern browser with JavaScript and WebAssembly enabled. No account or Python installation is needed for the online activities. A laptop or tablet with a keyboard makes editing easier; phones also support reading and short experiments. Allow the first Python run time to download the engine, around 10 MB.

Each browser keeps its own drafts and completion checkpoints. On a shared computer, use separate browser profiles or export each learner’s progress before another person uses the same profile. There is no teacher dashboard or automatic cloud sync.

A first session: predict, run, explain

  1. Meet the idea. Read What is a program? together. Ask the learner to describe an everyday task as a sequence of steps.
  2. Make a prediction. Open the first Python activity. Before pressing Run, ask what text should appear and why.
  3. Try the missing expression. Let the learner control the keyboard. Use the first hint if needed, then the closer hint. If you load the answer, read it aloud together before running.
  4. Change one thing. Alter a message or a value. Predict whether it changes the output, causes an error or does nothing.
  5. Explain the evidence. Compare the result with the prediction. Ask which line accounts for the difference. Stop at a comfortable point; there is no timer.

How do I know they understand?

A completed checkpoint means the output matched the example. It is not a grade. Look for the ability to explain a line, predict a small change and repair a mistake. Ask “What would happen if…?” before suggesting the answer.

Make room for different learning speeds

There are no locked activities, countdowns or public scores. Read the concept guide first if the story activity feels too fast. Return to a worked example when needed, then change a small part to make it personal. Pair learners by having one type while the other predicts; swap roles regularly.

The Python syntax guide helps with quotes, colons and indentation. The debugging guide shows how to treat an error as evidence. These are useful pauses, not penalties.

Where should we go next?

Continue through the learning trail in order, or follow the activity number in the book. Save the game lab for later if you want to avoid story spoilers. Use the Python playground for independent experiments and Your progress to export activity drafts.

Read privacy and accessibility information before using shared devices. For print and Kindle edition updates, visit the book page.