systematic-debugging

To identify a root cause before fixing, follow a structured debugging approach that enforces evidence gathering and pattern analysis across four distinct phases. This prevents symptom-focused remedies and reduces wasted effort on incorrect patches.

The best way to debug flaky tests systematically is to apply a phase-based methodology starting with root cause investigation, followed by pattern analysis and hypothesis testing. This isolates intermittent failures rather than masking them with retries.

Handling production incidents under pressure requires a systematic debugging process that enforces explicit evidence gathering and stack-trace instrumentation. This structured approach prevents rushed, symptom-focused fixes during critical outages.

You should use systematic debugging for troubleshooting complex systems, integration failures, and performance problems. It is essential when you need to build defense-in-depth validations to ensure your fixes are robust and maintainable.

Phase-based systematic debugging consists of four steps: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You must complete all four phases in order before proposing or applying any code fixes.

Your bug fix likely causes new issues because it addresses symptoms rather than root causes. Applying a systematic debugging methodology with defense-in-depth validations ensures the underlying problem is resolved without introducing regressions.