Start with a temperature fan that won’t spin — English carousel cover for this classroom case
Parents ask it often: what if kids quit the moment they hit an error? In our Markham classroom the honest answer is simple — name what is broken first, then fix. Do not swap projects the moment something fails. Four questions on paper beat a restart.
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 they swap the project.
A real classroom case: temperature-controlled fan that stopped
Last month at afterschool in Markham we had a temperature-controlled fan project. When it gets hot, the fan should cool the air. The fan stopped. One classmate wanted to start over. We paused and wrote four questions on paper before touching the wires.
|
Goal hot → fan cools air |
State read · compare · on/off |
Done air when hot · quiet when cool |
Edges sensor · threshold · cable · strip |
Once those four answers are clear, “what is broken” is clearer than “scrap it and restart.” The typing (or the rewiring) is the fast part. Our 2026-09-22 Xiaohongshu note used this exact classroom beat: write what is broken first, then fix — do not swap projects.
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. “When it is hot, the fan runs and cools the air” is a different job from “make any fan spin.” If a kid (or an AI prompt) muddles those, the fix that comes back solves the wrong problem.
- The useful state is tiny on purpose. You only hold read → compare → on if hot → off if cool. That is abstraction: keep what the next check needs, drop the rest.
- The done rule and edge cases are the algorithm. The same four questions transfer to an oven preheat check, a washer weird-noise check, or a bike chain that slipped. 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 swap the project.
Three steps kids can name
We practice the same shape on the bench:
1 · See — the sensor and the temperature-fan goal
2 · Judge — apply the four rules and edge cases
3 · Mission — finish the clear plan and fix, don’t swap projects
see the sensor and the goal → judge with the four rules and edge cases → finish the clear plan and fix, don’t swap projects
Computational thinking kids can own — before AI types a line.
- Decomposition — goal → state → done rule → special cases
- Abstraction — keep only read → compare → on if hot → off if cool
- Algorithms — read → compare → on/off → handle sensor loose / threshold too high / fan cable loose / power strip off
- Pattern recognition — same four questions in oven preheat, washer weird-noise, bike chain slip, contest-style I/O
Try this at CodeSky Markham
Walk-in coding afterschool for ages 7–18. Think first, then fix — 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-22-孩子一遇到报错就放弃怎么办 (temperature-controlled fan case; Python → JavaScript → C++ pathway; contest-style disclaimer).
