systematic-debugging

Systematic debugging is a structured four-phase workflow to identify root causes before applying fixes. You need it for complex systems, flaky tests, or debugging under time pressure across development, staging, and production environments.

To find the root cause, follow the four phases in order: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. Each phase has explicit prerequisites that must be met before advancing to the next.

The best way to stop shortcut fixes is to enforce anti-patterns and defense-in-depth practices during debugging. This approach mandates strict phase ordering and hypothesis testing to ensure robust root-cause resolution.

Yes, this systematic debugging workflow applies to flaky tests and production failures. It provides practical guidance for real-world scenarios, ensuring you identify root causes even under time pressure in complex systems.

Your debugging process misses the root cause when skipping prerequisites between phases. Enforcing a strict four-phase workflow with pattern analysis and hypothesis testing prevents superficial fixes and targets the source.