Technologies · Year 2

Active learning ideas

Debugging Basics: Finding the Glitches

Active learning works for debugging basics because young children develop logical reasoning through physical actions. When students move or build according to instructions, they see errors in real time. This immediate feedback helps them connect glitches in sequences to the steps that caused them.

• ACARA Content Descriptions
• AC9TDI2P03

• 20–35 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 25 min · Pairs

Partner Navigation: Buggy Directions

One partner gives a sequence of directions with a deliberate error to guide the other around a taped floor grid to a target. The follower acts it out exactly and reports the mismatch. Partners switch, predict the glitch first, then fix it together.

Differentiate between an intended action and an actual outcome in a sequence.

Facilitation Tip

During Partner Navigation: Buggy Directions, position yourself to observe pairs and step in if they skip systematic checking, such as reading all instructions before starting.

What to look for

Provide students with a simple algorithm, such as instructions for drawing a smiley face, with one deliberate error (e.g., 'draw a circle' then 'draw two eyes inside the circle' instead of 'on the circle'). Ask students to draw what the instructions actually produce and then circle the instruction that caused the difference.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Think-Pair-Share
• 30 min · Small Groups

Block Sequence Fix: Tower Challenges

Provide cards with step-by-step instructions to build a specific block tower, including one or two errors. In small groups, students predict issues, build anyway, note failures, then revise and rebuild correctly. Record changes on worksheets.

Predict where an error might occur in a given set of instructions.

Facilitation Tip

During Block Sequence Fix: Tower Challenges, provide a limited set of blocks so students focus on sequence rather than material constraints.

What to look for

Present a scenario: 'Imagine you gave your friend instructions to build a tower with three blocks, but they built a tower with only two blocks.' Ask students: 'How could you figure out which step was missed or done incorrectly? What would be your first step to fix it?'

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 03

• Think-Pair-Share
• 35 min · Whole Class

Class Arrow Hunt: Group Algorithm

Project or display a sequence of arrow cards for the whole class to follow by moving desks or bodies. Pause when the error appears, discuss predictions, vote on fixes, then test the corrected version as a group.

Design a strategy to systematically find and fix a mistake in a simple algorithm.

Facilitation Tip

During Class Arrow Hunt: Group Algorithm, assign roles like ‘reader’ and ‘checker’ to ensure every student contributes to the debugging process.

What to look for

Give each student a card with a short, buggy algorithm (e.g., '1. Stand up. 2. Hop on one foot. 3. Sit down. 4. Clap your hands.'). Ask them to write down what would happen if step 3 was 'Stand up again' instead of 'Sit down', and then suggest one way to check instructions to avoid this mistake next time.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 04

• Think-Pair-Share
• 20 min · Individual

Pattern Card Debug: Individual Check

Give each student a printed sequence of shapes or colors with errors. They draw or color the expected outcome first, follow steps, identify glitches, and rewrite the algorithm correctly before sharing with a neighbor.

Differentiate between an intended action and an actual outcome in a sequence.

Facilitation Tip

During Pattern Card Debug: Individual Check, circulate with a checklist to note which students rely on random guesses versus logical steps.

What to look for

Provide students with a simple algorithm, such as instructions for drawing a smiley face, with one deliberate error (e.g., 'draw a circle' then 'draw two eyes inside the circle' instead of 'on the circle'). Ask students to draw what the instructions actually produce and then circle the instruction that caused the difference.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Teach debugging by modeling slow, deliberate checking of each step in a sequence. Avoid rushing to fixes. Research shows that young learners benefit from verbalizing their thought process aloud while following instructions. Use simple, familiar tasks like lining up or building with blocks to ground the concept in their daily experience. Emphasize that debugging is a skill, not a test of perfection.

Successful learning looks like students identifying errors in sequences, explaining why they happened, and correcting them step-by-step. They should work collaboratively to test predictions and revise instructions. By the end, students should confidently check algorithms for accuracy and completeness.

---

Watch Out for These Misconceptions

• During Partner Navigation: Buggy Directions, students may think errors only happen when directions are given digitally.

  Use physical movement sequences with clear visual or auditory cues to show that glitches occur in all instructions. After an error, ask students to act out the corrected version to reinforce that debugging applies to human actions.

• During Block Sequence Fix: Tower Challenges, students may try random changes to fix a tower that doesn’t match the goal.

  Pause the activity and model a step-by-step check from the first block to the last. Ask students to point to the step where the tower deviates from the picture. Emphasize that fixes should target the cause, not just the result.

• During Class Arrow Hunt: Group Algorithm, students might assume there is only one error in a long sequence.

  Intentionally include two or three errors in the arrow path. During the hunt, ask groups to list every place the path doesn’t match the intended destination. Use peer questioning to challenge assumptions about single errors.

---

Methods used in this brief

• Think-Pair-Share