systematic-debugging

Root cause investigation follows a structured four-phase workflow: first, gather evidence and isolate the failure; second, identify patterns across failures; third, test hypotheses against the evidence; fourth, implement fixes targeting the actual cause. This prevents temporary patches that mask underlying issues.

Systematic debugging enforces investigation before fixes through phase-by-phase checklists, anti-pattern detection, and cross-component evidence gathering. The workflow ensures you understand what broke and why before proposing solutions, applicable to test failures, production bugs, performance problems, and integration issues.

The root cause mandate enforces the iron law: no fixes without root cause investigation first. Anti-rationalization rules and explicit red flags resist the temptation of shortcuts under time pressure, ensuring fixes address actual causes rather than symptoms.

Yes. The framework applies to any bug, test failure, or unexpected behavior, even in emergencies. Anti-rationalization rules and mandatory phase-by-phase investigation help you resist pressure to skip diagnosis, preventing wasted time on ineffective patches.

Symptom-based fixes mask underlying issues, leading to repeated failures and wasted debugging time. Root cause fixes address the actual problem through disciplined investigation, pattern analysis, and hypothesis testing, ensuring lasting solutions and deeper problem understanding.

Apply structured debugging whenever you encounter bugs, test failures, unexpected behavior, performance problems, builds, or integrations. Random fixes lead to new bugs and poor understanding; systematic investigation prevents false starts and ensures fixes work across all cases.