debugginglisted

# Debugging ## Coverage - Reproduction: turning a vague bug report into a deterministic failing case - Scope reduction: isolating the smallest surface where the failure still reproduces - Evidence capture: collecting logs, stack traces, and state snapshots at the moment of failure - Root-cause isolation: distinguishing symptoms from causes and resisting the urge to patch symptoms - Fix verification: re-running the original failure path to confirm the fix is real - Regression prevention: converting the failing case into a permanent test so the same bug cannot return silently ## Philosophy The fastest way to fix a bug is usually the wrong fix. A working reproduction is worth more than a plausible hypothesis; a plausible hypothesis is worth more than a clever fix; a clever fix that skips the reproduction step ships the same bug again under a different name. When pressure is high the temptation to jump from symptom to patch is also high — resist it, because the cost of a wrong fix is paid again by the next person who hits the same failure with less context than you had. ## Workflow Each step asks a question. The answer decides the next step. Do not skip steps to save time; the steps exist because skipping them is how bugs return. | Step | Ask | If yes | If no | |---|---|---|---| | 1. Reproduce | Do you have a deterministic failing case? | Go to step 2 | Add logging, narrow inputs, or run the failing path in a loop until the failure is reliable | | 2. Scope | Can you reprod