systematic-debugging

Root cause analysis requires enforcing a strict investigation phase before making any code changes. By reading error messages carefully and identifying the true origin of the failure first, you stop symptom-chasing and prevent wasted debugging time.

Debugging production incidents under pressure requires a systematic four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and verified implementation. This structured approach prevents random changes and ensures effective incident resolution.

Debugging build failures and integration issues systematically involves moving through root cause investigation, pattern analysis, minimal hypothesis testing, and verified implementation to identify the real failure origin before changing code.

When a fix fails to resolve unexpected behavior, you must stop and reanalyze the problem. The stop-and-reanalyze rule forces you back to root cause investigation and pattern analysis rather than attempting further random code changes.

Hypothesis testing can fix performance problems in development by applying minimal changes and verifying results. This systematic debugging approach ensures you confirm the root cause through pattern analysis before full implementation.