Debugging Language
From reading stack traces to writing P1 incident messages — practise the English vocabulary and structures you need across the debugging workflow. 5 practice sets.
Reading Error Messages
Parse stack traces and error messages into plain English for teammates and tickets.
Describing the Problem
Write specific bug reports using Expected vs. Actual, steps to reproduce, and environment.
Debugging Narration
Narrate your debugging process: noticed / hypothesis / tested / found / fixed.
Uncertainty & Hypotheses
Express confidence levels in debugging — hedge precisely with "might", "likely", "confirmed".
Incident Communication
Write P1 initial messages, status updates, and all-clear postmortem summaries.
Quick reference
Error message vocabulary
- stack trace: the call chain showing where an error occurred
- exception: an error event that disrupts normal execution
- null pointer / NullReferenceException: accessing a property of null
- unhandled rejection: a Promise that rejected with no catch handler
- segfault (segmentation fault): process accessed memory it shouldn't
- 404 / 500: not found / internal server error
- timeout: operation took longer than the allowed time limit
Debugging narration phrases
- "I noticed that…" — observation
- "My hypothesis is…" / "I suspect…" — unverified theory
- "I tested this by…" — verification step
- "I confirmed / ruled out…" — result
- "The root cause was…" — conclusion
- "The fix was to…" — resolution
- "Expected: X — Actual: Y" — standard bug report format
Uncertainty hedges
- "might be" — low confidence, a guess
- "could be" — plausible possibility
- "likely" — moderate-high confidence
- "probably" — high confidence, not yet verified
- "confirmed that" — verified, certain
- "not sure yet" — still investigating
- "ruling out…" — actively eliminating a hypothesis