systematic-debugging

Systematic debugging prevents symptom-focused work by enforcing an explicit no-fixes rule until root cause investigation is complete. It uses a four-phase workflow to identify why bugs occur before proposing any software fixes.

The best way to debug production incidents is applying a structured debugging workflow with anti-pattern awareness. This includes data-flow tracing and stack-trace logging to identify root causes across pattern analysis and hypothesis testing phases.

To stop fixing symptoms, enforce the Iron Law of debugging: no fixes without root cause investigation first. This structured approach mandates identifying the actual root cause through hypothesis testing before moving to the implementation phase.

Systematic debugging is explicitly designed for test failures, production incidents, and performance problems. It implements four phases starting with root cause investigation, ensuring you apply defensive practices like defense-in-depth before implementation.

Common debugging anti-patterns include skipping root cause investigation and applying fixes prematurely. The systematic debugging workflow defends against these by enforcing pattern analysis, stack-trace logging, and data-flow tracing before any implementation.