systematic-debugging

Systematic debugging finds the root cause of bugs by enforcing a mandatory four-phase process: root cause investigation, pattern analysis, single-hypothesis testing, and minimal implementation with verification. This approach prevents guess-and-check loops by requiring evidence before any fixes are attempted.

Debugging race conditions in multi-component systems requires tracing data flow across component boundaries and adding diagnostic instrumentation before proposing any fixes. Systematic debugging enforces this evidence-first approach to identify concurrency issues and timing failures.

To stop guess-and-check loops when fixing test failures, apply systematic debugging with explicit stop conditions that trigger when fixes fail repeatedly or evidence is insufficient. The process requires reading errors carefully, reproducing consistently, and completing root cause investigation before proposing fixes.

Use systematic debugging for production incidents and performance problems whenever guessing would waste time or mask the real trigger. It applies pressure-resistant decision rules that enforce root cause investigation before fixes, even when working under incident response pressure.

To verify a bug fix without introducing new issues, use verification guardrails that demand a minimal failing test case and confirm the fix without stacking multiple changes at once. This systematic approach ensures single-hypothesis testing validates the root cause resolution.