systematic-debugging

Systematic debugging is a disciplined root-cause investigation process used when software bugs or test failures occur. Apply it to stop symptom-patching and prevent repeated failures by isolating the underlying issue before proposing any fixes.

To debug test failures without patching symptoms, follow a four-phase workflow: investigate errors, analyze patterns, form and test a hypothesis, then implement only the root-cause fix. Create a failing regression test case before changing code to verify the fix.

Trace production bugs across multiple components by instrumenting and isolating failures across boundaries like API, service, and database. Gather evidence across these integration points during root-cause investigation before altering any code.

The best way to diagnose build and integration failures is to read the full error and reproduce it reliably with the exact command. Then proceed to pattern analysis and hypothesis testing to implement a regression-proof root-cause fix.

Yes, systematic debugging works for unexpected behavior and performance regressions. It forces evidence gathering and hypothesis testing to find the exact trigger, ensuring you fix the actual regression rather than applying a superficial patch.

Your software fixes keep causing repeated failures because you are patching symptoms instead of finding the root cause. You must complete evidence gathering, pattern analysis, and hypothesis testing before implementing a targeted fix to break this cycle.