systematic-debugging

Root-cause debugging requires a four-phase framework: investigate to find the actual source, analyze patterns across the codebase, form and test hypotheses, then implement verified fixes. This prevents recurring bugs by addressing the underlying problem, not just masking symptoms.

Recurring bugs signal symptom-based fixes. Use systematic investigation to identify the root cause before any change, test one modification at a time with reproducible evidence, and verify the fix prevents recurrence. This permanent approach replaces guesswork and quick patches.

Time pressure tempts quick fixes that mask deeper issues. A formal debugging process with mandatory root-cause investigation, pattern analysis, and hypothesis testing maintains discipline under stress, preventing shortcuts that cause future problems and waste more time later.

Multi-component failures require disciplined investigation to isolate the actual source. The four-phase framework—investigation, pattern analysis, hypothesis formation, and verified implementation—cuts through complexity by enforcing evidence-based reasoning instead of random code changes.

Unfocused fixes often target symptoms in one area while leaving the root cause intact in another. Systematic debugging with one-change-at-a-time testing and reproducible evidence gathering ensures fixes address the actual problem and don't introduce side effects.

Root-cause investigation distinguishes symptoms from causes through pattern analysis and hypothesis testing. Once you've traced the failure back through the codebase to its source and verified the fix prevents recurrence, you've found the real bug.