systematic-debugging

To find the root cause before fixing a bug, follow a systematic debugging workflow that enforces stepwise evidence gathering, reproduction, recent-change review, and data-flow tracing to pinpoint the actual source of failure rather than just treating the symptom.

The best way to troubleshoot flaky tests and build failures is to compare against working examples, form a single hypothesis, and test minimally to confirm the real source of the unexpected behavior across logs, code, and environment state.

Fixing a symptom instead of the root cause leads to repeated failures because the underlying fault remains in the code, causing wasted time and brittle patches that fail again when the same data-flow or environmental condition triggers the issue.

To debug production incidents and performance regressions across multiple components, trace the failure across logs, code, and environment state, then verify the root cause by creating a failing test before proposing any remediation.

Yes, systematic debugging is specifically designed for multi-component failures where the symptom is not the source, requiring pattern comparison and single-hypothesis testing to trace data-flow and isolate the true fault.