systematic-debugging

Systematic debugging is a structured investigation method that uncovers root causes before applying fixes. Use it for production issues, test failures, and performance problems to avoid quick patches that mask underlying issues.

To find a root cause, follow a four-phase investigation: reproduce the issue consistently, collect evidence and trace data flow, verify hypotheses across components, and establish a clear root cause before implementing any fix.

The best way to fix recurring bugs safely is to enforce root-cause analysis first, implement the fix only after validation, and add regression tests to ensure the error does not reappear or create new side effects.

Investigate production issues and test failures by reading error messages, reproducing the problem consistently, gathering evidence, and testing hypotheses systematically across affected components before proposing fixes.

Quick patches lead to new bugs because they mask underlying issues without resolving the actual root cause. Structured error analysis and hypothesis testing are required to ensure validated implementation and prevent recurring failures.