Activity 01
Peer Teaching: The Bug Swap
Students intentionally introduce one 'logic bug' into a working piece of code and then swap computers with a partner. The partner must use debugging strategies (like adding print statements) to find and fix the error, then explain the fix to the original creator.
Construct conditional statements using logical operators to achieve specific outcomes.
Facilitation TipDuring The Bug Swap, circulate and listen for students explaining their fixes aloud to catch gaps in their logic before they finalize solutions.
What to look forPresent students with a series of simple Boolean expressions using AND, OR, and NOT (e.g., `True AND False`, `False OR True`, `NOT True`). Ask them to write down the resulting truth value for each expression on a mini-whiteboard or paper.
UnderstandApplyAnalyzeCreateSelf-ManagementRelationship Skills
Generate Complete Lesson→· · ·
Activity 02
Gallery Walk: User Feedback Loop
Students display their current projects on their screens. Classmates rotate around the room, testing the programs and leaving 'I like...', 'I wish...', and 'What if...' feedback on sticky notes to guide the next stage of refinement.
Analyze how logical operators alter the truth value of expressions.
Facilitation TipDuring the Gallery Walk, ask each group to prepare one key piece of feedback about a user scenario before moving on to the next station.
What to look forPose a scenario: 'Imagine you are programming a game where a player can only pick up a special item if they have enough points AND they are at a specific location. How would you use logical operators to write the condition for picking up the item? What if the item could be picked up if they had enough points OR if a secret code was entered?' Facilitate a class discussion on their approaches.
UnderstandApplyAnalyzeCreateRelationship SkillsSocial Awareness
Generate Complete Lesson→· · ·
Activity 03
Inquiry Circle: Error Log Analysis
Provide groups with a series of error messages from a common programming language. Students must work together to 'decode' what the computer is trying to say and suggest the most likely fix for each scenario.
Justify the choice of 'AND' versus 'OR' in different programming scenarios.
Facilitation TipDuring Error Log Analysis, provide a color-coded answer key so students can self-check their logic traces without direct teacher input.
What to look forGive students a simple problem: 'Write a conditional statement that checks if a user's age is between 13 and 18 (inclusive) AND if they have parental consent.' Ask them to write the code snippet and briefly explain why they chose AND.
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→A few notes on teaching this unit
Teach logical operators by connecting them to everyday decisions first, then mapping those decisions to code. Avoid abstract truth tables without context. Research shows that students grasp operators faster when they see concrete consequences—like doors opening or items collecting in games—rather than just symbols on a page.
Successful learning looks like students confidently evaluating Boolean expressions, explaining their reasoning, and revising code based on feedback. They should use AND, OR, and NOT to solve real-world problems and recognize logic errors in working programs.
Watch Out for These Misconceptions
During The Bug Swap, watch for students who assume that if their code runs without an error message, it must be correct.
Use the Bug Swap checklist to guide students to compare their code against the original requirements—not just the absence of syntax errors. Require them to run test cases and record outputs before swapping.
During the Gallery Walk, watch for students who believe debugging is a sign they are bad at coding.
Use the Gallery Walk feedback sheets to highlight that every piece of software undergoes testing. Frame each bug as a puzzle to solve together, not a personal failure.
Methods used in this brief