systematic-debugging

Systematic debugging prevents symptom fixes by enforcing a four-phase progression: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You must gather evidence and complete each phase before moving forward.

Systematic debugging handles multi-component issues by enforcing strict phase progression: investigate root causes, analyze patterns, test hypotheses, and implement fixes. It adds defense-in-depth validations across multiple layers to prevent future regressions.

To stop fixing symptoms, follow anti-shortcut rules during debugging: STOP and re-analyze if jumping to conclusions, NEVER fix the symptom directly, and document all evidence. Complete root cause investigation before proposing any fixes.

Yes, systematic debugging applies to test failures, production outages, flaky tests, and complex integrations across multi-component systems. It enforces evidence gathering and hypothesis testing to ensure accurate root cause identification before fixing.

Apply defense-in-depth validations by adding checks at multiple layers during the Implementation phase. This systematic debugging practice prevents regression after you fix the identified root cause of the software issue.