01 · Foundations — The Foundational Debugger¶
◉ What This Section Is About¶
Every programmer encounters errors. The difference between a programmer who grows and one who stays stuck is not talent or luck — it is whether they have a repeatable process for understanding what went wrong.
This section builds that process from the ground up.
Before reaching for a search engine, before asking a friend, before opening an AI chat window — there is information already on your screen. An error message. A highlighted line. A stack trace in the output window. This section teaches you to read all of it, interpret it, and act on it deliberately.
The habits built here are not just for beginners. They are the foundation that every more advanced debugging skill is built on. A programmer who skips this foundation does not become a faster debugger — they become a faster guesser.
The standard
"If you cannot identify the error type, location, and message — you are not debugging yet."
◉ Who Should Read This Section¶
Read this section if any of the following applies to you:
- You are writing your first programs and errors feel overwhelming
- You close the error window quickly and start changing code randomly
- You reach for a screenshot before reading the error message
- You ask for help before engaging with the information already on your screen
- You have been programming for a while but never formally learned a debugging workflow
This section is the right starting point regardless of which language or IDE you are using.
◉ Pages in This Section¶
| Page | What It Covers |
|---|---|
| Understanding Errors | The four error types — syntax, runtime, logical, and semantic — what they are, when they occur, and what they tell you |
| Reading Error Messages | How to read an error message as a sentence, locating the source, understanding a stack trace at a basic level |
| The Basic Debugging Workflow | The six-step repeated workflow: STOP, identify, locate, compare, change one thing, test |
| Asking for Help (Human or AI) | What makes a good question, the non-negotiable checklist, why screenshots are not enough |
| Foundation Exercises | ▣ Practical exercises — classify errors, read messages, locate sources across multiple languages |
◉ What This Section Does Not Cover¶
This section does not teach you how to use a debugger tool (breakpoints, step-through, watch windows), how to investigate complex multi-file bugs, or how to debug framework-driven systems. Those belong in 02 · Investigation and beyond.
If you are already comfortable with everything in this section, that is the right place to go next.
Continue to: Understanding Errors →