Week 11 · 45-60 min

Debugging and Error Handling

Week Summary

A quick preview of the main ideas in this week before you begin the slides.

Review these key terms before starting this week. They are kept simple so students can learn the new vocabulary before moving into the slides.

Slide 1💡

Progress

1 / 8

Learning goal

Identify, understand, and fix errors in code.

Read one card at a time. Focus on the main idea first, then look at the visual on the right to help it stick.

Debugging means finding and fixing bugs.

It is a normal part of programming.

Reading error messages is an important debugging skill.

Testing small pieces of code helps isolate problems.

Patience and persistence matter a lot.

Remember

Debugging is not a failure, it is how programmers improve code.

Slide 1 of 8

Use arrows or dots to move through the lesson

Coming Next Week: Next: Review and Mini Projects

Complete the "Build a Command-Line Program" project across weeks 11-12.

Day 1: Choose a project type and sketch the program flow on paper.
Day 2: Set up variables, input prompts, and the basic structure in Thonny.
Day 3: Write functions for each major piece of logic.
Day 4: Add conditionals to handle different outcomes or paths.
Day 5: Add a loop so the program can repeat or process multiple items.
Day 6: Add a list or dictionary to store structured data such as questions, scores, or items.
Day 7: Add basic error handling with try/except for invalid input.
Day 8: Test with normal, edge, and invalid inputs, then fix bugs.
Day 9: Add comments explaining each important part of the code.
Day 10: Present the program live and explain design choices and challenges.