Session 1 · DESIGN: Sketch
Algorithm to code
- 10 minTurn each storyboard panel into steps (pseudocode) before you touch Scratch.
- 35 minBuild version one: main sprite, the object to catch or answer, score, and an ending.
- 5 minSave a copy called 'v1' so you can always go back.
Session 2 · DESIGN: Improve
Bug hunt
- 10 minDebugging strategies: read the code aloud, test one change at a time, explain it to a rubber duck.
- 20 minFix four planted bugs in the teacher's buggy project. Record each: what happened, why, how you fixed it.
- 15 minSwap games with a partner. Try to break theirs. Log the bugs you find.
- 5 minStart your bug log in your design journal.
Getting started
Fix the bugs in order; each one has a hint card.
Stretch
Write a custom block to replace code you repeated three times.
Checkpoint
A playable version one and a bug log with at least three bugs found and fixed.
Activities for this week
- The buggy project: What are the most common kinds of bugs, and how do you track them down?
Useful this week
- Code Club Aotearoa ↗ Free step-by-step coding projects and volunteer-led clubs for kiwi kids.
- Introduction to Scratch projects ↗ Starter game projects you can follow, then change.
- Algorithms ↗ Why some sets of steps are faster and better than others.