Think the problem first — English carousel cover for this classroom case

Parents often hear “syntax and commands” when a kid answers what coding is for. In our Markham classroom we flip that: start with a small everyday school mess, then break it into steps a kid can finish.

A real classroom case: the duty roster

Last week the case was the classroom duty roster. Who wipes the board, who empties the recycling, who leads the line — and on which day. On paper that sounds simple. Then someone is out, someone wants to swap, and the same kid keeps getting the heavy jobs. The paper stops working and the class starts arguing.

Once those four answers are clear, the kid has a sketch that can become code. The typing is the fast part. Our 2026-09-15 Xiaohongshu note used this exact classroom beat: clear thinking first, grammar second.

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.

1. AI does not remove the need to name the goal. “Keep duty fair across the week” is a different job from “print a pretty list of chore names.” If a kid (or an AI prompt) muddles those, the code that comes back solves the wrong problem.
2. The useful state is tiny on purpose. You only hold who, which day, and which task. That is abstraction: keep what the next step needs, drop the rest.
3. The done rule and edge cases are the algorithm. The same four questions transfer to a homework due reminder, seat rotation, or a group-task split. 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.
4. Languages are tools on a path, not the answer. Early work often uses Python so logic lands fast; JavaScript when the same idea becomes something clickable on a page; C++ later when speed and structure matter. Tools change; the four questions do not.

So AI’s presence does not cancel a thinking-first start. It raises the value of kids who can decompose, hold the right state, and name the edge cases before they ask a model to type.

Three steps kids can name

We practice the same shape on the bench:

1 · See — the messy duty list

2 · Judge — apply the rules and edge cases

3 · Mission — finish a fair rotation

• Decomposition — goal → state → done rule → special cases
• Abstraction — keep only who, day, and task the next step needs
• Algorithms — assign → remember → finish the round → roll the next one
• Pattern recognition — same four questions in homework reminders, seat rotation, group-task splits, contest-style I/O

Follow CodeSky

Instagram @codeskyca  ·  小红书 / RedNote  ·  WeChat 公众号: search codeskyca

Sources: CodeSky Xiaohongshu note pack 2026-09-15-学编程到底学什么 (classroom duty roster case; Python → JavaScript → C++ pathway; contest-style disclaimer).