Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Know that bugs are normal.
- ✓Follow steps to fix a mistake.
- ✓Find the wrong step.
- ✓Fix and check it.
What do you do when your code does not work?
Order the Fixing Steps
Project this and have students put the steps for fixing a mistake in order.
45 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Oops!
What do you do when your program does the wrong thing?
👩🏫 Teacher Moves
- Run a program with a bug.
- Ask what to do.
- Set the goal.
🎒 Student Actions
- Look.
- Guess.
- Get ready.
Use — Fixing Mistakes
Students use the steps.
👩🏫 Teacher Moves
- Send students to Order the Fixing Steps.
- Order the steps.
- Note run → find → fix → run.
🎒 Student Actions
- Order.
- Say.
- Note it.
Modify — Find the Bug
Students modify.
👩🏫 Teacher Moves
- Point to the step that goes wrong.
- Guess the cause.
- Mark it.
🎒 Student Actions
- Point.
- Guess.
- Mark.
Create — Fix It
Students create.
👩🏫 Teacher Moves
- Fix a mistake in a program.
- Run it again.
- Check it works.
🎒 Student Actions
- Fix.
- Run.
- Check.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Say the first step.
- Say what debugging means.
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say.
- Complete the exit ticket.
Built to the standards you report on
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Test and debug a program to make sure it runs.
Create programs with sequences & loops.
Decompose a problem to find the bug.
Test and fix solutions.
One lesson, every learner
Multilingual Learners
- Fixing-step cards.
- Frame: “run, find, fix, check.”
- Think aloud a fix.
Support & Access
- Use 3 steps.
- Fix one simple bug.
- Use a checklist.
Stretch & Extend
- Find 2 bugs.
- Explain the fix.
- Help a partner debug.
What to gather
- 📽️Screen / board
- 🐛Fixing-step cards
- 💻Order the Fixing Steps
- 🎮A buggy program
- 📓Notebooks
- 🎫Exit-ticket slips
Key terms — hover for a quick definition
Exit Ticket
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Reflect: fixing mistakes.
Have students list the steps to fix a mistake. A printable debugging worksheet is in the Computer Science library.
Study the key terms
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
Nice work!
Check your understanding
A quick self-check with instant feedback, drawn from this lesson’s key terms.
Nice work!
Printable worksheet
A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.
Part A · Write the word that matches each meaning
- to find and fix a bug
- make sure it works
- run it after fixing
- a mistake in code
- make the program go
- something not quite right
- correct the step
- locate the wrong step
Part B · Show what you learned
- What is fixing a mistake in code called?
- What is the first step?
- What do you do after you fix a step?
Part B: 1) Debugging. 2) Run the program and watch what happens. 3) Run it again to check.