systematic-debugging

Systematic debugging applies a four-phase framework: root-cause investigation to reproduce and trace the bug, pattern analysis to compare against known-good behavior, hypothesis testing with minimal changes, and targeted implementation with regression tests. This ensures fixes address the underlying cause, not symptoms.

Root-cause investigation traces data flow and collects exact error messages to locate where the bug originates in multi-component systems. For concurrency issues like race conditions and deadlocks, this phase isolates the timing or synchronization failure before any fix is attempted.

Start with Phase 1: reproduce the failure exactly, inspect error messages, and confirm the failure scenario. Pattern analysis then compares the failure against known-good references to identify what changed, forming the basis for a single testable hypothesis before implementation.

Yes. Evidence collection through instrumentation and logging guidelines ensures you gather concrete data about system state and behavior. This supports root-cause investigation and hypothesis testing while minimizing guesswork and unnecessary code changes.

The framework includes escalation rules that trigger when initial hypotheses fail or when bugs span multiple systems. These rules guide you to re-examine assumptions and adjust your investigation strategy rather than implementing speculative fixes.