Activity 01
Pair Programming: Loop Replacement
Pairs examine a code with repeated movement blocks for a character animation. They identify the pattern, insert a loop block, and test both versions to compare length and smoothness. Pairs record one key change and its benefit before sharing.
Analyze how using loops can make code more concise and efficient.
Facilitation TipDuring Pair Programming: Loop Replacement, circulate and ask each pair to explain why they chose a loop over repeated blocks before they test it.
What to look forProvide students with two code blocks that achieve the same visual effect: one using repetition and one using a loop. Ask them to write one sentence explaining which is more efficient and why. Then, present a simple scenario, like 'If the score is 10, play a sound,' and ask them to write the conditional statement.
UnderstandAnalyzeEvaluateSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 02
Small Groups: Conditional Showdown
Groups receive a sorting task code with basic if statements. They experiment with if-else or nested options, run scenarios, and vote on the best structure with reasons. Groups demo their choice to the class.
Justify the choice between different conditional structures for a given problem.
Facilitation TipIn Small Groups: Conditional Showdown, listen for explanations that compare if versus if-else using real examples from their trial runs.
What to look forDisplay a short, repetitive code segment on the board. Ask students to hold up fingers to indicate how many lines of code they think would be saved by using a loop. Then, ask them to verbally explain the condition that would control the loop.
UnderstandAnalyzeEvaluateSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 03
Whole Class: Live Refactor Demo
Display an inefficient class project code on the interactive board. Solicit student suggestions for loops or conditionals, implement changes live, and run before-and-after tests together. Discuss observations as a group.
Design a more efficient version of an existing code segment.
Facilitation TipFor the Whole Class: Live Refactor Demo, invite students to predict the next line of refactored code before you type it to keep them actively thinking.
What to look forStudents share a small code project they have refined. Their partner reviews the code and answers two questions: 'Did you find a place where a loop could make the code shorter?' and 'Is the conditional logic clear?' Partners then discuss their feedback.
UnderstandAnalyzeEvaluateSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 04
Individual: Project Polish Challenge
Students select a prior coding project and hunt for repetitions or clunky decisions. They apply loops or refined conditionals, test thoroughly, and note efficiency improvements in a reflection log.
Analyze how using loops can make code more concise and efficient.
What to look forProvide students with two code blocks that achieve the same visual effect: one using repetition and one using a loop. Ask them to write one sentence explaining which is more efficient and why. Then, present a simple scenario, like 'If the score is 10, play a sound,' and ask them to write the conditional statement.
UnderstandAnalyzeEvaluateSelf-ManagementSocial Awareness
Generate Complete Lesson→A few notes on teaching this unit
Teaching efficiency in code benefits from letting students experience the pain of repetition firsthand, then guiding them to discover loops as the natural solution. Avoid giving the answer too soon. Instead, ask questions that help students compare messy code to clean code. Research shows that seeing the reduction in lines and errors is more convincing than any explanation.
By the end of these activities, students will confidently replace repeated instructions with loops, justify their choice of conditional structures, and explain how these choices improve their programs. They will also demonstrate this skill by polishing a segment from their creative projects.
Watch Out for These Misconceptions
During Pair Programming: Loop Replacement, watch for students who believe loops add lines instead of reduce them.
Ask pairs to count the lines in their original repeated block and the loop version, then ask which version is easier to change if they need to add another repetition.
During Small Groups: Conditional Showdown, watch for students who assume all conditionals are interchangeable.
Hand each group a scenario card with a single outcome and ask them to try both if and if-else, then discuss which structure matches the scenario better.
During Whole Class: Live Refactor Demo, watch for students who think efficiency is only about speed.
Show the refactored code side-by-side with the original and point out how the new version is easier to read and update, then ask students to name one maintenance task that would be simpler.
Methods used in this brief