Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Find a bug.
- ✓Read error messages.
- ✓Change one thing.
- ✓Re-test.
What do you do when your code doesn’t work?
Order the Debugging Steps
Project this and have students put the debugging steps in order.
50 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — It Broke!
Your program crashes — what’s your very first move?
👩🏫 Teacher Moves
- Pose the question.
- Share ideas.
- Set the goal.
🎒 Student Actions
- Think.
- Share.
- Get ready.
Use — Debugging
Students learn.
👩🏫 Teacher Moves
- Send students to Order the Debugging Steps.
- Order the steps.
- Note change ONE thing.
🎒 Student Actions
- Order.
- Say.
- Note it.
Modify — Debug It
Students practice.
👩🏫 Teacher Moves
- Read an error message.
- Find the line.
- Guess the fix.
🎒 Student Actions
- Read.
- Find.
- Guess.
Create — Create
Students apply.
👩🏫 Teacher Moves
- Debug a broken program.
- Change one thing.
- Re-test it.
🎒 Student Actions
- Debug.
- Change.
- Re-test.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- What’s the first step?
- Why change one thing at a time?
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say it.
- 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.
Systematically test and debug programs.
Give attribution and iterate on code.
Document programs to aid debugging.
Troubleshoot computational problems.
One lesson, every learner
Multilingual Learners
- Debugging-step cards.
- Frame: "first I notice, then ___."
- Debug a tiny program.
Support & Access
- Use 3 core steps.
- Fix one small bug.
- Use a checklist.
Stretch & Extend
- Debug a logic error.
- Use print statements.
- Debug a partner’s code.
What to gather
- 📽️Screen / board
- 🐛Debug-step cards
- 💻Order the Debugging Steps
- 📄Buggy code snippet
- 📓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: debugging.
Have students debug a broken program one step at a time. A printable buggy-code sheet is in the CS 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
- find and fix a bug
- a clue about a problem
- correct the problem
- an error in code
- follow the code
- code runs but is wrong
- check if code works
- a typo in the code
Part B · Show what you learned
- What is the first debugging step?
- Why change one thing at a time?
- What should you do after a fix?
Part B: 1) Notice the program isn’t working right. 2) So you know which change fixed it. 3) Run it again to check.