systematic-debugging

Systematic debugging enforces root-cause investigation before applying fixes, preventing random patches that waste time and mask underlying software issues. It requires tracing data flow and completing all four investigation phases before implementation.

Debug production issues methodically by applying explicit anti-shortcuts and stop rules. Complete Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation phases sequentially to resist time pressure and avoid creating new bugs.

The best way to find root causes of performance problems is tracing data flow across multiple layers. Add instrumentation for forensics, validate data at multiple layers, and establish a failing test before writing a fix.

Use a phase-based debugging process whenever facing software bugs, test failures, or production issues to prevent quick patches from creating new bugs. Violating this methodical process violates the spirit of effective debugging.

Defense-in-depth debugging works for complex software bugs by validating data at multiple layers and adding instrumentation for forensics. This approach ensures thorough root-cause investigation before moving to hypothesis testing and implementation.