systematic-debugging

The systematic debugging workflow has four phases: root cause investigation, pattern analysis, hypothesis and testing, and implementation. You must complete Phase 1 before proposing any fixes to avoid symptom-driven patches.

Trace data flow and complete root cause investigation before proposing any fixes. Reproduce the bug consistently, then investigate the underlying cause to avoid surface-level patches and reduce regressions in production incidents or test failures.

Rushed, surface-level fixes that address symptoms rather than the root cause are common debugging anti-patterns. The systematic approach identifies explicit failure modes and applies defense-in-depth validations to resist these problematic patterns.

Yes, systematic debugging applies to build failures and performance problems. It provides guidance for operations issues such as test failures, production incidents, performance problems, and build or integration failures.

Avoid using a four-phase debugging workflow for trivial, isolated issues needing a quick fix. This approach is designed for complex bugs requiring root-cause investigation, pattern analysis, and defense-in-depth validation to prevent regressions.