The Sage DadWork · Wisdom · WonderFree activities

A computer science guide for parents and teachers

You can be curious together.

You don’t need to know assembly or have the answer ready. Ask for a prediction, try it, and notice one change. Let your child hold the mouse—and let yourself be surprised.

Start with the paper activity. Take turns at the keyboard. It’s fine to stop after one discovery. Use age for support and experience for the entry point. A 13-year-old beginner belongs at the beginning; a younger learner can explore a stretch with support.

Ready for home, homeschool, or classroom

A lesson plan you can actually use.

Choose a starting point · Open the two hands-on starter lessons

Before learners arrive

Read the selected lesson’s goal and prerequisite. Gather paper and counters; one device per pair is enough for the adventures. Try the original program once. No learner account or software installation is needed. The browser lab requires JavaScript; the hands-on starters work without it.

A 30-minute teaching rhythm

  1. 0–5 min · Connect: introduce the goal and act it out with paper.
  2. 5–8 min · Predict: each learner says, draws, or writes what will happen.
  3. 8–18 min · Investigate: one learner operates; one watches the values. Swap roles halfway.
  4. 18–25 min · Transfer: change one thing and test a fresh prediction.
  5. 25–30 min · Explain: collect an exit ticket and choose the next step.

For a 45-minute class, add 10 minutes for the stretch and 5 for pairs to compare explanations. For younger learners, stop after 10–15 minutes and resume another day.

Support by age, without an ability ceiling

4–6 · Explorers
Adult reads. Use gestures, drawings, and large paper pieces. Work in 5–10 minute bursts; skip written code. Avoid small counters where they are unsuitable.
7–9 · Discoverers
Use 10–20 minutes, read together, and move a counter for each step. Let the learner explain aloud.
10–12 · Strategists
Use 20–30 minutes. Compare two traces and ask for a reason, not just a number.
13+ · Thinkers
Use 25–40 minutes. Beginners still start with sequence; experienced learners test a counterexample and inspect the code.

Assess the explanation, not the clicks

Use the selected lesson’s exit ticket to decide the next teaching move.
EvidenceWhat you hear or seeNext move
Needs supportGuesses the answer but cannot show the steps.Return to paper; model one step, then let the learner try.
DevelopingTraces correctly with a prompt; explanation is incomplete.Try a new starting value with a partner.
Ready to extendPredicts, traces, and explains an unfamiliar example independently.Move to the next lesson or its stretch.

Exit ticket: “I predicted ___. I observed ___. The instruction that explains the difference is ___. On a new example, I would ___.” Accept speech, pointing, a drawing, or a written trace. Completion badges show an activity was explored; they are not evidence of mastery.

Common misconceptions to listen for

Shared devices and learner privacy

The existing adventures save applied programs, notes, and place in this browser. They are not a class roster, gradebook, or cloud record. Ask learners to avoid names or personal information in notes. On a shared device, use Clear saved adventure progress before changing learners, or a fresh browser profile. Keep assessment records in your school’s approved system. The new selector keeps choices only in the page URL; it does not create learner profiles. Existing site analytics and consent controls remain in place.

LearnRisc status: the handoff is pending. All current lessons use paper or the limited practice simulator. Planned connected labs will be released only after their capabilities and learning outcomes are verified.