systematic-debugging

Systematic debugging is a four-phase method that identifies the root cause of bugs before proposing fixes. It requires reading errors, reproducing the issue, and tracing data flow through system boundaries to prevent symptom-focused work.

Start phase-based troubleshooting by reading errors, reproducing the issue, and gathering evidence. You must complete the root cause investigation phase before moving to pattern analysis, hypothesis testing, or implementation.

Defense-in-depth debugging validates fixes across entry points, business logic, environment, and instrumentation. This layered approach catches edge cases by tracing data flow through multi-component stacks and verifying fixes with targeted tests.

You should use hypothesis testing after completing root cause investigation and pattern analysis. This gating ensures you validate data tracing evidence before implementation, preventing fixes that only address symptoms rather than the underlying fault.

Yes, the systematic debugging framework is applicable to software debugging, test failures, and production issues. It enforces root-cause investigation and defense-in-depth across data flow and system boundaries for all these scenarios.

Tracing data flow prevents symptom-focused fixes by enforcing root-cause investigation. It requires validating fixes with layered checks across entry points, business logic, environment, and instrumentation to catch edge cases across system boundaries.