Computer Science · 9th Grade

Active learning ideas

Looping Constructs (For/While)

Looping constructs can feel abstract to students until they see how iteration structures match real problems. Active learning turns the abstract into concrete by forcing students to choose, justify, and refactor loops in front of peers. This topic benefits from discussion, collaboration, and hand-tracing, because the difference between a correct loop and a misleading one often lies in one character or boundary condition.

• Common Core State Standards
• CSTA: 3A-AP-15

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

Activity 01

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: Which Loop Fits?

Post six short task descriptions (for example: print each name in a roster, keep asking until the user enters a number, count from 1 to 20). Students independently choose for or while for each and write one-sentence justifications. Pairs compare choices, resolve disagreements, then share edge cases with the class to build a shared decision rule.

Compare when it is more effective to use a 'for' loop versus a 'while' loop.

Facilitation Tip

During Jigsaw: Loop Pattern Reference Cards, give each group a blank template with loop types on one side and example problems on the other to make the patterns explicit and reusable.

What to look for

Present students with two code snippets, one using a 'for' loop and one using a 'while' loop, to achieve the same outcome (e.g., printing numbers 1-10). Ask students to identify which loop is more appropriate and explain why in one sentence.

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

Activity 02

• Experiential Learning
• 35 min · Pairs

Pair Programming: Trace Before You Run

Give pairs five short loop snippets, including at least one off-by-one error and one potential infinite loop. Partners alternate driver and navigator, hand-tracing each loop on paper to predict the output before running. After execution, each pair identifies what their trace missed and writes a rule to catch that mistake next time.

Design a loop to iterate through a list of items and perform an action on each.

What to look for

Provide students with a scenario: 'A program needs to ask a user for their age until they enter a number between 18 and 65.' Ask students to write the initial structure of the loop they would use (either 'for' or 'while') and state the condition that would terminate the loop.

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Activity 03

• Gallery Walk
• 30 min · Pairs

Gallery Walk: Refactor the Repeated Code

Post five code samples around the room that accomplish repeated tasks using copy-pasted statements instead of loops. Pairs rotate through each station, rewrite the code using an appropriate loop on a sticky note, and label the loop type with a brief reason. A closing class discussion surfaces cases where students disagree and examines why one choice is still preferred.

Evaluate the efficiency of different looping strategies for a given task.

What to look for

Pose the question: 'Imagine you are writing a program to count the total number of steps in a marathon. Would you use a 'for' loop or a 'while' loop? Explain your reasoning, considering what information you have before the loop starts and what might change during its execution.'

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 04

• Jigsaw
• 40 min · Small Groups

Jigsaw: Loop Pattern Reference Cards

Assign each group one common loop pattern to become experts on: accumulator, counter-controlled, sentinel-value, or list traversal. Groups study worked examples and build a one-page reference card explaining when and how to use their pattern. Students then rotate to teach their pattern to peers from other groups, assembling a class library of loop patterns to reference throughout the unit.

Compare when it is more effective to use a 'for' loop versus a 'while' loop.

What to look for

Present students with two code snippets, one using a 'for' loop and one using a 'while' loop, to achieve the same outcome (e.g., printing numbers 1-10). Ask students to identify which loop is more appropriate and explain why in one sentence.

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

A few notes on teaching this unit

Teachers often start with hand-tracing to show how loops change state each iteration, because students overlook boundary conditions until they write out each step. Avoid rushing to coding before students can explain why a loop stops, especially with while loops where the exit condition depends on changing data. Research shows that students grasp iteration faster when they compare structurally similar problems side-by-side and articulate the difference in one sentence.

Students will confidently select the appropriate loop based on what they know before the loop starts versus what changes during execution. They will explain their choice in writing and identify off-by-one errors by tracing the first and last iterations. Peer feedback helps students recognize when code communicates intent versus when it only runs without errors.

---

Watch Out for These Misconceptions

• During Think-Pair-Share: Which Loop Fits?, watch for students who argue that 'for' and 'while' loops are interchangeable without citing clues like known sequence length or changing condition.

  During Think-Pair-Share: Which Loop Fits?, ask students to label each problem with two clues: what they know before the loop starts and what might change during execution. Then have them present which loop they chose and explain how the clues match the loop type.

• During Pair Programming: Trace Before You Run, watch for students who declare the loop correct after it runs without errors, even if the output skips or duplicates values.

  During Pair Programming: Trace Before You Run, require students to fill a trace table for the first and last two iterations before running code. If they cannot explain why the loop stops at the right place, they must revise the condition or update statement.

• During Gallery Walk: Refactor the Repeated Code, watch for students who remove nested loops entirely because they assume nesting is always inefficient.

  During Gallery Walk: Refactor the Repeated Code, give each group a sticky note labeled 'Why nest?' and ask them to place it next to any nested loop they decide to keep, explaining the task structure that requires it.

---

Methods used in this brief

• Think-Pair-Share
• Experiential Learning
• Gallery Walk
• Jigsaw