Expected result
State what should happen before changing code.
Curriculum topic
Debugging
Debugging is the disciplined work of explaining the difference between what a system should do and what it actually does.
Why it matters
A small idea that returns in larger systems.
Every substantial project contains surprises. Debugging teaches students to slow down, preserve evidence, test one idea at a time, and treat a bug as a clue rather than a judgment about ability.
Real-world connection
Repairing a bicycle, tracing a circuit, and debugging a game all depend on separating symptoms from causes. Random changes can hide information; a controlled test creates it.
The connection shows where the idea returns; it does not claim every advanced application is taught in this first topic.
Math and logic kernel
The structure beneath the project.
Observed result
Describe what actually happened without guessing why.
Hypothesis
Choose one possible cause.
Controlled test
Change or inspect one relevant thing.
Small examples
Make one relationship visible at a time.
Show coordinates
Inspect position when movement seems wrong.
Display state
Reveal whether the game thinks it is playing or finished.
Reduce the system
Test one sprite, sensor, or rule alone.
Reproduce the bug
Find a repeatable sequence that causes the problem.
Program connections
Where this topic appears.
Active now
Scratch & Game Design
Beginner-friendly programming through original games, animations, simulations, and interactive stories.
Active now
Robotics
Commands, sensors, simple electronics, simulations, and physical systems organized around Sense, Decide, Act.
Available later
Roblox Studio / Lua
A future bridge from visual programming to Lua, 3D objects, events, and larger game systems.
Available later
AI & Smart Machines
A future practical and critical program about patterns, predictions, prompts, limits, and human judgment.
Common mistakes
Useful clues, not reasons to stop.
Changing many things
The project works again but nobody knows which change mattered.
Testing only success
The easiest path works while boundaries remain broken.
Blaming the tool
A precise program rule is overlooked because the result feels unreasonable.
Fixing the symptom
Extra code covers the visible problem while the underlying state remains wrong.
Lesson and projects
Use the idea inside a working system.
Scratch & Game Design
Complete downloadable pilot
Escape from the Giant Pigeon
Build a fast chase game with known positions, collision rules, win and loss states, and reliable restart behaviour.
Open project
Robotics
Guided Class Project
Robot Maze Logic
Plan, predict, and debug a robot route using paper, a grid simulation, or optional hardware.
Open project
Robotics
Guided Class Project
micro:bit Reaction Timer
Measure reaction time, store results, and decide what makes a timing test fair.
Open project