Activity 01
Inquiry Circle: The Multiplier Effect
Give students a simple 'clicker' game script. In small groups, they must change the code so that clicking a 'power-up' sprite doubles the score instead of just adding one. They then test each other's games to see how the difficulty changes.
Explain how mathematical operators are used to change a score variable.
Facilitation TipDuring Collaborative Investigation, circulate and ask each pair to trace their number line with their finger as they explain their script’s effect to you.
What to look forPresent students with short code snippets. Ask them to identify whether the code is 'setting' or 'changing' a variable and to predict the final value of the variable after execution.
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→· · ·
Activity 02
Simulation Game: Physical Collision Logic
One student acts as a 'sprite' and another as a 'variable manager' holding a whiteboard with a number. When the sprite 'collides' with a specific object in the room, the manager must update the number based on a rule (e.g., 'if touch red, minus 5').
Differentiate between changing a variable and setting a variable.
Facilitation TipWhile running the Physical Collision Logic simulation, pause the game at key moments and ask students to predict what the variable will do next before the code runs.
What to look forGive each student a card with a game scenario (e.g., 'Player collects a coin', 'Player hits an enemy'). Ask them to write one code-like instruction to change a relevant variable (e.g., 'change score by 10' or 'change health by -5').
ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson→· · ·
Activity 03
Think-Pair-Share: Set vs Change
Provide pairs with a list of game events (e.g., 'Game Over', 'Collect a Coin', 'Level Up'). They must decide whether each event should 'set' the variable to a specific number or 'change' it by a certain amount and explain why.
Design a penalty system that reduces a player's health in a game.
Facilitation TipUse the Think-Pair-Share to assign half the class to defend 'set' and half to defend 'change' before switching sides, forcing them to internalize both perspectives.
What to look forPose the question: 'Imagine a game where you lose points for missing a target. How would you use variables and operators to design this penalty system? What happens if you accidentally set the score to 0 instead of changing it?'
UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson→A few notes on teaching this unit
Teachers approach this topic by grounding abstract changes in concrete, physical actions. Start with a number line or counter so students see that 'change by -1' is a movement, not a destination. Avoid teaching operators in isolation—always tie them to real events like collisions or clicks to prevent the 'automatic update' misconception. Research shows that students grasp variable updates better when they physically act out the change before coding it.
Successful learning looks like students confidently distinguishing between setting and changing variables, writing correct code snippets for each case, and explaining why sequence matters in updates. You’ll see students debugging each other’s scripts and correcting peers when variables don’t behave as expected.
Watch Out for These Misconceptions
During Collaborative Investigation, watch for students who think 'change by -1' and 'set to -1' are the same. Redirect them by having them mark their number line: start at 5, 'change by -1' to 4, then 'set to -1' to jump to -1.
During Collaborative Investigation, remind students that 'change' moves relative to the current value, while 'set' jumps to an absolute value. Use a shared number line on the board to demonstrate both operations step by step.
During Physical Collision Logic, watch for students who assume the variable updates automatically when the sprite collides. Redirect by having them trace the code line-by-line and identify the missing 'change score' block.
During Physical Collision Logic, pause the simulation at collision points and ask students to read the code aloud, line by line, to locate where the variable change is triggered. Peer-checking their printed scripts helps them spot missing links.
Methods used in this brief