systematic-debugging

Systematic debugging enforces a four-phase framework that mandates root-cause investigation before any fix. Start by reading error messages carefully, reproducing the issue consistently, checking recent changes, gathering evidence across components, and tracing data flow. Only after completing Phase 1 investigation do you proceed to fixes, ensuring solutions are permanent and don't introduce new problems.

Root-cause investigation requires careful analysis of error messages, consistent reproduction of the failure, review of recent code changes, and evidence collection across all system components. Trace the data flow to pinpoint the exact failure point and its underlying cause rather than applying quick fixes that mask symptoms.

Formulate a single, testable hypothesis and make the smallest possible change to validate it. This hypothesis-driven testing approach replaces shotgun debugging by enforcing evidence-based investigation first. Compare broken code with working examples to identify differences and understand dependencies before attempting any fix.

Yes. The four-phase framework applies to any technical issue—test failures, production bugs, performance problems, builds, and integrations. It's especially effective under time pressure when quick fixes seem tempting, ensuring thorough investigation yields durable solutions across all failure types.

Investigation before fixes prevents wasted time on guess-and-check debugging and ensures solutions address root causes, not symptoms. Thorough investigation eliminates recurring bugs, prevents new problems from incomplete fixes, and saves significant development time through permanent, durable solutions.