systematic-debugging

To find the root cause of a bug, follow a disciplined four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This prevents symptom fixes by enforcing analysis before applying fixes.

Debugging a production outage across multi-service architectures requires a systematic approach using pattern analysis and hypothesis testing. A phase-driven investigation identifies root causes before implementation, applying defense-in-depth practices to prevent recurring failures.

Systematically debug flaky test failures by applying root cause investigation and pattern analysis before fixing. The framework enforces non-skipping rules, requiring you to STOP and re-analyze under pressure to avoid patching symptoms.

Defense-in-depth debugging works for complex software development failures by applying multi-layer validation and instrumentation. This framework enforces a strict four-phase process to ensure fixes target actual root causes rather than surface symptoms.

The limitation of systematic debugging during high-pressure incidents is the temptation to skip phases. The framework mitigates this with anti-shortcut guidance, forcing you to STOP and re-analyze complexity rather than rushing a premature fix.

Start root cause tracing by executing Phase 1 through Phase 4 in strict order before attempting any fix. This requires pattern analysis and hypothesis testing to validate the true source of the failure across your architecture.