systematic-debugging

Systematic debugging is a disciplined, multi-phase approach to diagnosing and resolving bugs. It is essential for production bugs, test failures, flaky behavior, and complex multi-component systems where quick symptom fixes risk masking the actual root cause.

To start systematic debugging, read error messages thoroughly, reproduce the issue reliably, and begin Phase 1: Root Cause Investigation. You must complete this investigation phase before proposing or implementing any code fixes.

The four phases of systematic debugging are Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This workflow enforces thorough analysis and includes defense-in-depth strategies to prevent symptom fixes.

Yes, systematic debugging works for flaky behavior and test failures. It enforces root-cause investigation before any fixes and applies explicit anti-pattern rules with defense-in-depth strategies to ensure thorough multi-component system analysis.

Fixing a symptom instead of finding the root cause risks masking bugs because quick patches do not address the underlying failure. Systematic debugging resists these shortcuts through explicit rules and defense-in-depth strategies during pattern analysis and hypothesis testing.

The limitation of quick patches is that they fail to ensure reproducibility and thorough root-cause analysis. Without systematic debugging's explicit rules and defense-in-depth strategies, quick fixes often mask underlying issues in complex multi-component production systems.