Sensing User Input with Variables

Active learning works because debugging requires students to slow down and observe code behavior firsthand. When learners manipulate variables and test inputs themselves, they move beyond accidental fixes to intentional troubleshooting. This topic demands hands-on practice to build the habits of systematic debugging that will serve students in more advanced programming tasks.

• Year 6
• Computing
• 3 activities
• 20 min–40 min

Learning Objectives

1. Design a simple game or interactive animation that responds to keyboard input using variables to store key states.
2. Compare the effectiveness of different sensing blocks (e.g., 'key pressed?', 'mouse down?') for controlling character actions.
3. Explain how variables are used to store and update information about user interactions, such as movement direction or button presses.
4. Analyze a given script to identify how variables are updated based on user input and how this affects program behavior.

Mock Trial

⏱ 30 min·Small Groups

Mock Trial: The Case of the Broken Code

The teacher presents a 'crime scene' (a broken program). Students act as detectives to find the 'culprit' (the specific line of code) and present evidence of why it caused the crash.

Prepare & details

Differentiate between passive and active sensing in a program.

Facilitation Tip: During Mock Trial, prepare a scripted role for yourself as the 'judge' to model questioning techniques that guide students toward logical reasoning.

Setup: Desks rearranged into courtroom layout

Materials: Role cards, Evidence packets, Verdict form for jury

• Analyze
• Evaluate
• Create
• Decision-Making
• Social Awareness

Peer Teaching

⏱ 20 min·Pairs

Peer Teaching: Debugging Swap

Students intentionally hide one bug in their own code and swap with a partner. The partner must find the bug and write a short 'bug report' explaining the fix.

Prepare & details

Evaluate the effectiveness of different sensing methods for a user-friendly interface.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Stations Rotation

⏱ 40 min·Small Groups

Stations Rotation: Debugging Techniques

Set up stations for different techniques: 'Rubber Ducking' (explaining code aloud), 'Dry Running' (tracing on paper), and 'Breakpoints' (pausing code). Students rotate to solve mini-puzzles at each stop.

Prepare & details

Design a game where a character's movement is controlled by user input stored in variables.

Setup: Tables/desks arranged in 4-6 distinct stations around room

Materials: Station instruction cards, Different materials per station, Rotation timer

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Teaching This Topic

Teach debugging by modeling your own thought process out loud. Use a 'think-aloud' while working through student errors, making your reasoning visible. Avoid rushing to fix errors for students; instead, scaffold their observation skills. Research shows that students learn debugging best when they practice in low-stakes, collaborative environments where mistakes are expected and discussed openly.

What to Expect

Success looks like students using structured methods to isolate issues, explaining their thought process clearly, and collaborating to find solutions. They should be able to trace variable changes and predict program behavior before testing. Peer feedback and self-reflection become natural parts of their debugging routine.

Watch Out for These Misconceptions

Common Misconception

During Mock Trial, students may believe debugging is just 'guessing' until it works.

What to Teach Instead

Use the structured worksheet prompts in Mock Trial to enforce a 'Predict-Test-Observe' cycle. Before any changes are made, students must write their prediction of the bug’s location, the test they’ll run, and the expected outcome.

Common Misconception

During Station Rotation, students may assume that if the code runs without crashing, there are no bugs.

What to Teach Instead

Include logic errors in the Station Rotation activities that produce no syntax errors but incorrect behavior. Have students test for expected outcomes, such as a score increasing when it should decrease, and use peer feedback sheets to highlight these 'hidden' bugs.

Assessment Ideas

Quick Check

During Mock Trial, present students with a short code snippet and ask them to predict the outcome when a key is pressed. Have them explain their reasoning by tracing the variable changes on a provided worksheet.

Exit Ticket

After Peer Teaching: Debugging Swap, students write down two variables they would use to control a jumping character and explain what each variable stores and how it changes when the spacebar is pressed.

Peer Assessment

After Station Rotation: Debugging Techniques, students swap projects and provide feedback on whether the input is responsive and whether variables are clearly used to control movement, using a feedback sheet with specific prompts.

Extensions & Scaffolding

• Challenge early finishers to create a hidden bug in a partner's code that can only be found by tracing variables through multiple user inputs.
• Scaffolding: Provide a partially completed 'Debugging Checklist' template with prompts like 'What should happen when the key is pressed?' and 'What variables change?'
• Deeper exploration: Introduce conditional logic errors by giving students a simple game where variables update incorrectly, requiring them to trace the flow of conditions and variable assignments.

Key Vocabulary

Sensing Blocks	These are special blocks in programming environments that detect external actions, like keyboard presses, mouse movements, or even physical sensor data.
Variable	A named storage location in a program that can hold a value, such as a number or text, which can change during the program's execution.
Event Handling	The process of detecting and responding to specific occurrences or 'events' within a program, such as a user clicking a button or pressing a key.
Boolean Variable	A variable that can only hold one of two values: true or false. Often used to track states, like whether a key is currently being pressed.