systematic-debugging

Systematic root-cause debugging is a four-phase framework to uncover the true cause of technical issues before fixing them. Use it for production outages, test failures, performance problems, and integration issues to prevent wasted effort on symptom fixes.

Debug a production outage by following four phases in order: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. Document findings at each phase and complete Phase 1 before proposing any fixes to ensure you address the actual root cause.

Yes, this systematic debugging process applies to flaky tests, integration failures, performance problems, and production outages across any technology stack. It adapts to various scenarios by enforcing root-cause investigation before any code changes are implemented.

The best way to create failing tests after root-cause analysis is leveraging Phase 4 of the process, which uses test-driven development to implement fixes. This ensures your changes are validated by a failing test that confirms the root cause before the fix is applied.

Yes, systematic debugging relies on identifying anti-patterns during the Pattern Analysis phase to recognize recurring bad practices. This step ensures you understand the underlying patterns causing the issue before moving to hypothesis testing and implementation.

You must complete root-cause investigation first because skipping it leads to symptom fixes and rework, especially under time pressure. This disciplined approach reduces wasted effort by ensuring all changes target the true underlying issue.