systematic-debugging

Systematic debugging is a structured method to diagnose bugs by enforcing root-cause investigation before proposing fixes. Use it for test failures, production defects, integration issues, and performance problems, especially under time pressure.

To find a root cause, follow a four-phase workflow: Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. Reproduce the issue, check recent changes, and use diagnostic instrumentation before attempting any fixes.

When fixes fail under time pressure, apply stop-and-reanalyze rules to resist quick fix temptations. After multiple failed fixes, stop patching, question the architecture, and revert to evidence-first pattern analysis.

Debug test failures in multi-component systems by applying minimal-change hypothesis tests during the Hypothesis and Testing phase. Add diagnostic instrumentation to gather evidence across components before implementing any architectural changes.

The best way to debug production defects is using evidence-first debugging. Enforce the root-cause mandate by reproducing the defect, checking recent changes, and running minimal-change hypothesis tests before applying any implementation.

Question architecture during root cause analysis when multiple fixes fail repeatedly. The workflow includes stop-and-reanalyze rules that trigger an architecture review after repeated hypothesis failures to identify systemic pattern issues.