
Start with a four-week Scratch chase game — English carousel cover for this classroom case
Parents ask it often: how long until a kid can build something real? In our Markham classroom the honest answer is about four weeks for a small playable build — when the plan is written first. Four questions on paper beat waiting to feel ready.
Why this matters
AI can type code. It cannot replace a kid who can name the goal, hold the right state, and check the edge cases — before week one of a real build.
A real classroom case: four-week Scratch chase game
Last month at afterschool in Markham we did not open Scratch first. We built a Scratch chase game over four weeks. A character chases an apple and the score goes up. On paper that sounds simple. Then the score sticks at 0, the chase never starts, a kid wants to quit mid-week because it felt too hard, or the file is not saved before a station switch. The build stops being a plan and starts being a stall.
|
Goal chase apple · score up |
State move · score · chase · polish |
Done classmate plays · no explaining |
Edges score 0 · no chase · quit · unsaved |
Once those four answers are clear, the four-week path shows up. The typing (or the Scratch blocks) is the fast part. Our 2026-09-21 Xiaohongshu note used this exact classroom beat: write the plan first, then open Scratch.
Why this still matters when AI can write code
Claims below are grounded in that teaching note — not an external product case with published accuracy metrics.
- AI does not remove the need to name the goal. “Character chases an apple and the score goes up” is a different job from “make a pretty game screen.” If a kid (or an AI prompt) muddles those, the code that comes back solves the wrong problem.
- The useful state is tiny on purpose. You only hold the week plan — move, then score, then chase, then polish. That is abstraction: keep what the next step needs, drop the rest.
- The done rule and edge cases are the algorithm. The same four questions transfer to a science fair board plan, a birthday invite checklist, or a team sports rotation. Contest-style questions inspired by CCC Junior, CCC, BCC, and school contests reuse those moves — kids who want to sit those register on their own; CodeSky is not an official contest program and is not affiliated with Waterloo or CEMC.
- Languages are tools on a path, not the answer. Early work often uses Python so the steps stay readable; JavaScript when the same idea becomes something clickable on a screen; C++ later when speed and structure matter. Tools change; the four questions do not.
So AI’s ability to type code does not cancel a thinking-first start. It raises the value of kids who can name the goal, hold the right state, and check the edge cases before they ask a model to type — and before they open Scratch for week one.
Three steps kids can name
We practice the same shape on the bench:

1 · See — the four-week Scratch chase goal

2 Judge — apply the four rules and edge cases

3 · Mission — finish the clear four-week plan, then open Scratch
see the four-week Scratch chase goal → judge with the four rules and edge cases → finish the clear plan, then open Scratch
Computational thinking kids can own — before AI types a line.
- Decomposition — goal → state → done rule → special cases
- Abstraction — keep only move, then score, then chase, then polish
- Algorithms — move → score → chase → polish → handle score 0 / no chase / quit mid-week / unsaved file
- Pattern recognition — same four questions in science fair boards, birthday invites, team rotations, contest-style I/O
Try this at CodeSky Markham
Walk-in coding afterschool for ages 7–18. Think first, then build — that is what we practice on the bench.
9833 Markham Rd Unit 2, Markham, ON L6E 0E5
Email info@codesky.ca · Comment TRIAL on Instagram @codeskyca
Follow CodeSky
Instagram @codeskyca · 小红书 / RedNote · WeChat 公众号: search codeskyca
Sources: CodeSky Xiaohongshu note pack 2026-09-21-学多久才能做出真正作品 (four-week Scratch chase game case; Python → JavaScript → C++ pathway; contest-style disclaimer).
