Ninth graders learn the two main kinds of bugs — syntax errors (the code breaks the language’s rules and won’t run) and logic errors (the code runs but does the wrong thing). Knowing which is which makes debugging faster. They sort the errors, then find both.
Students will be able to…
Why does some broken code refuse to run, while other broken code runs but is wrong?
Project this and sort each into Syntax error or Logic error.
Tap any phase to open the teacher moves and student actions.
One program won’t run; another runs but gives a wrong answer. Why?
Students learn.
Students practice.
Students apply.
Students close.
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Identify and fix syntax and logic errors.
Evaluate program correctness.
Document debugging.
Troubleshoot systematically.
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Have students find and fix one syntax and one logic error. A printable error sheet is in the CS library.
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
A quick self-check with instant feedback, drawn from this lesson’s key terms.
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.