systematic-debugging

Systematic root-cause debugging is a four-phase workflow that traces bugs to their original cause using evidence collection and hypothesis testing. Use it when quick patches mask underlying issues or when troubleshooting unexpected behavior across codebases and production systems.

Begin root-cause debugging by gathering error details and reproducing the issue before proposing any fixes. This initiates Phase 1, enforcing disciplined investigation steps and phase boundaries to prevent symptom-level patches and ensure durable resolutions.

The best way to prevent symptom-level patches is applying defense-in-depth checks during root-cause debugging. This enforces phase boundaries between pattern analysis, hypothesis testing, and implementation to ensure robust, durable resolutions instead of temporary quick fixes.

Random fixes create new bugs because they waste time and mask underlying issues without addressing the actual defect. Root-cause debugging prevents this by tracing failures to their original cause through disciplined evidence collection and verified fixes.

Yes, this debugging workflow applies to production system outages. It guides investigations from evidence collection to verified fixes across codebases and production systems, tracing unexpected behavior to its root cause through a structured four-phase process.

Symptom-driven debugging limitations include masking underlying issues and creating new bugs through quick patches. Without systematic root-cause tracing, fixes remain temporary and lack the defense-in-depth checks required for durable, verified resolutions.