systematic-debugging

Systematic debugging is a phase-based methodology to identify root causes before fixes. Use it for software bugs, test failures, production incidents, and performance issues to prevent symptom-based patches.

To find the root cause of a failing test, follow a four-phase methodology: gather evidence, analyze patterns, test hypotheses, and implement safely. This ensures you resolve the actual failure, not just the symptom.

The best way to investigate production incidents is using defensive rules like "NEVER fix the symptom" and "STOP and re-analyze." This enforces evidence gathering and hypothesis testing to ensure root-cause resolution.

Yes, root-cause tracing works for build and performance issues. The methodology applies phase-based pattern analysis and hypothesis testing to systematically identify and resolve the underlying faults.

Stop symptom fixes during bug investigation by enforcing a four-phase framework with defensive rules. Mandate evidence gathering and hypothesis testing before implementation to ensure root-cause-first resolution.

The limitation of phase-based debugging is the resistance to immediate fixes, requiring full evidence gathering and hypothesis testing before implementation. This methodical approach may slow down urgent symptom mitigation under pressure.