systematic-debugging

Systematic debugging prevents skipped investigation by enforcing a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. It resists time pressure by mandating evidence gathering before any fixes are applied.

Systematically debugging complex system failures requires completing four explicit phases with stop rules. You gather diagnostics, compare against references, and establish a reproducible root cause before implementation, escalating if the root cause remains unidentified.

A structured debugging workflow avoids premature conclusions by enforcing strict no fixes without root cause mandates. It uses anti-patterns to resist rationalization and time pressure, requiring evidence gathering and hypothesis testing before implementation.

Bug fixes introduce new issues when applied without identifying the root cause. Systematic debugging prevents this by enforcing evidence gathering, pattern analysis, and hypothesis testing across four phases before any implementation changes are made.

Yes, the four-phase systematic debugging process covers both simple bugs and complex systems. It scales by applying explicit Phase 1 to 4 steps, anti-patterns, and documentation requirements to any issue, escalating only if no root cause is found.

You should escalate a bug when the systematic debugging process cannot establish a root cause. The workflow includes explicit stop rules that trigger escalation if evidence gathering, pattern analysis, and hypothesis testing fail to identify the underlying issue.