You stare at your code. It runs. It crashes. It gives the wrong answer and you have no idea why. You try changing random things and hope something works. An hour later, you're more lost than before.

That's not debugging — that's guessing. Real debugging is a skill, and like any skill, it can be learned.

**TLDR: Debugging Strategies** is a concise, no-filler guide for high school and early college students who want to stop flailing and start solving problems systematically. You'll learn how to read error messages and stack traces in Python and JavaScript so you can extract real information instead of panic, how to use print statements and assertions the right way, and when to reach for a real debugger. You'll learn to isolate a bug, reproduce it reliably, and binary-search through code to find exactly where things go wrong.

For students who've wondered how to find and fix bugs in code without spending hours on a wild-guess loop, this guide delivers a clear mental framework: debugging is hypothesis testing, not random tweaking. The final section walks through the bug patterns students hit most often — off-by-one errors, null/undefined crashes, scope problems, type confusion — and shows how to prevent them before they start.

This book is for anyone learning to program: CS students, AP Computer Science Principles test-takers, self-taught coders, and tutors who need a tight reference for a session. It's short by design — you'll read it once and actually remember it.

Pick it up and stop guessing.

• Distinguish syntax errors, runtime errors, and logic errors and know which strategy applies to each
• Read stack traces and error messages to localize a bug quickly
• Use print debugging, assertions, and an interactive debugger effectively
• Apply systematic techniques like binary search, minimal reproducible examples, and rubber-duck debugging
• Recognize common bug patterns (off-by-one, null/undefined, mutation, scope) and how to prevent them

1. 1. What Debugging Actually Is
   Frames debugging as a structured investigation: forming hypotheses about why code misbehaves and testing them, not random tweaking.
2. 2. Reading Errors and Stack Traces
   How to extract real information from error messages, exceptions, and stack traces in Python and JavaScript.
3. 3. Print Debugging, Assertions, and Logging
   The simplest tools — print statements, asserts, and structured logs — and when each one is the right call.
4. 4. Using a Real Debugger
   Breakpoints, stepping, watch expressions, and inspecting state in IDE debuggers and pdb / Chrome DevTools.
5. 5. Systematic Strategies: Isolate, Reproduce, Bisect
   Higher-level techniques for hard bugs: minimal reproducible examples, binary search through code or commits, and rubber-duck debugging.
6. 6. Common Bug Patterns and How to Prevent Them
   A field guide to the bugs students hit most — off-by-one, null/undefined, scope, mutation, type confusion — with prevention habits.