systematic-debugging

Systematic debugging uses a four-phase framework: root cause investigation to gather evidence and reproduce the issue, pattern analysis to compare against working examples, hypothesis testing to verify a single cause, and implementation to fix and verify. This structured approach eliminates guesswork and saves time on failed patches.

Start with Phase 1 root cause investigation: read error messages, reproduce the bug reliably, check recent changes, and trace data flow across components. Never propose a fix before you understand the root cause; collecting evidence first prevents wasted effort on incorrect patches.

The systematic framework enforces Phase 1 investigation before any fix proposal, resisting the temptation for quick patches that mask symptoms. By understanding root cause first, you implement a single reliable fix rather than multiple failed attempts, actually saving time despite initial slowdown.

Systematic debugging applies to test failures, production bugs, performance problems, build issues, and integration failures. The four-phase framework—investigation, pattern analysis, hypothesis testing, and implementation—works across any technical incident where rapid diagnosis and reliable fixes matter.

Phase 3 hypothesis testing requires forming a single hypothesis first, then testing minimally to verify it. This replaces the anti-pattern of trying multiple fixes in parallel, which wastes time and obscures which change actually resolved the issue.