systematic-debugging

To prevent symptom-driven fixes, enforce root cause investigations before making any code changes. Systematic debugging uses a phase-based framework requiring documentation and explicit validation at every layer to ensure fixes address root causes.

The phase-based investigation framework guides teams through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It requires evidence gathering and data-flow tracing across complex multi-component systems before resolving production incidents.

Integrate test-driven development during the Hypothesis Testing and Implementation phases of debugging. Explicit validation and defense-in-depth checks ensure that code changes resolving test failures address the underlying root cause.

Common debugging anti-patterns involve taking shortcuts and applying symptom patches. Avoid them by applying defense-in-depth guidance, enforcing multi-layer validation, and documenting evidence for each phase before proposing fixes.

Systematic debugging applies across complex multi-component systems by enforcing data-flow tracing and evidence gathering. It guides teams through root cause investigations to prevent symptom fixes in distributed architectures.

Validate root cause hypotheses by applying defense-in-depth checks and explicit validation at every layer. The framework requires documenting the Pattern Analysis and Hypothesis Testing phases to ensure fixes address root causes.