systematic-debugging

Systematic debugging follows a four-phase framework: Root Cause Investigation gathers evidence about the failure, Pattern Analysis identifies recurring conditions, Hypothesis Testing validates assumptions, and Implementation applies the root-cause fix. This process prevents symptom-based patches that mask underlying issues.

Root cause analysis requires completing Phase 1 investigation before proposing any fix, even under pressure. Document evidence, perform pattern analysis to spot recurring triggers, formulate testable hypotheses, and only then implement lasting solutions. This resists the urge to patch symptoms.

Quick patches address symptoms rather than root causes, leaving underlying issues intact. This creates fragile software, prolongs debugging cycles, and frequently introduces new bugs. Systematic debugging enforces finding the true cause first, ensuring durable repairs.

Apply the four-phase framework to build and integration failures: investigate failure evidence with diagnostic instrumentation, analyze patterns across occurrences, test hypotheses about root causes, then implement solutions with traceability. This prevents jumping to configuration tweaks without understanding the failure.

Yes. Systematic debugging applies to unexpected behavior and performance problems by enforcing investigation before fixes, gathering measurable evidence, analyzing patterns, testing hypotheses, and implementing root-cause solutions with an anti-shortcut policy that maintains diagnostic traceability.

Rationalization counters address common excuses for bypassing the process—such as 'we'll patch it later' or 'this is faster.' Enforcing the four-phase framework and Iron Law policy, which mandates finding root causes before any fix, ensures disciplined debugging even in high-stakes scenarios.