systematic-debugging

Systematic debugging is a disciplined workflow that enforces root cause investigation before proposing fixes. It applies to code, tests, production incidents, and flaky failures, reducing wasted effort and false positives by avoiding symptom fixes.

To find the root cause, follow the four-phase systematic debugging workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation with guardrails. This structured approach ensures you locate the true source of the failure before coding.

Debug flaky test failures systematically by applying the four-phase workflow: investigate the root cause, analyze failure patterns, test hypotheses, and implement fixes with guardrails. This method prevents treating symptoms and ensures reliable resolution of intermittent issues.

The best way to investigate production incidents is using a phase-based debugging approach with defense-in-depth concepts. By enforcing Root Cause Investigation and Hypothesis Testing phases, you prevent symptom fixes and ensure the underlying issue is resolved.

Systematic debugging benefits from supportive skills like tests and verification-before-completion to validate hypotheses. While no strict dependencies are required, integrating these testing and verification practices strengthens the implementation phase guardrails.

Your bug fix likely addresses symptoms rather than the root cause. Systematic debugging prevents this by enforcing Pattern Analysis and Hypothesis Testing phases before implementation, applying defense-in-depth concepts to ensure the root cause is fully resolved.