systematic-debugging

Systematic debugging is a phase-based workflow that enforces root-cause investigation before proposing fixes. It structures troubleshooting into Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation to reduce time wasted on symptom fixes.

To troubleshoot flaky behavior and production bugs, read error messages and reproduce the issue consistently. Then complete all four debugging phases—investigation, analysis, hypothesis testing, and implementation—before proposing any fixes.

The best way to avoid symptom fixes is enforcing root-cause tracing first. By applying anti-pattern guidance and defense-in-depth validation, you resist shortcuts and ensure robust analysis before implementing any actual fixes.

Completing all four debugging phases matters because it ensures explicit root-cause tracing and defense-in-depth validation. Skipping phases leads to guesswork and symptom fixes, wasting time without resolving the real underlying issue.

You should not bypass root-cause first troubleshooting when facing production bugs, test failures, or flaky behavior. However, for immediate critical incident mitigation, applying temporary symptom fixes might be necessary before starting systematic investigation.