systematic-debugging

To find a root cause before fixing symptoms, follow a systematic debugging framework that enforces a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation. This prevents wasted effort on shortcut fixes.

The best way to debug production issues is applying a phased debugging framework that enforces root cause investigation, pattern analysis, hypothesis testing, and implementation with explicit defenses and phase gates to prevent premature patching.

To stop applying shortcut fixes when debugging test failures, use a defense-in-depth approach with explicit anti-pattern guidance and phase gates that force you to validate a root cause hypothesis before any implementation begins.

Yes, you can use a systematic debugging process for integration problems. The four-phase framework applies directly to integration issues by enforcing root cause investigation and hypothesis testing before applying any code fixes.

To validate a bug fix before completing implementation, follow the real-world testing and iteration patterns provided in the hypothesis testing and implementation phases to ensure your root cause analysis is correct.

You should avoid trial-and-error debugging when facing complex test failures, production issues, or integration problems, and instead use a systematic four-phase process to identify root causes and reduce rework.