systematic-debugging

Find the root cause of flaky tests by reproducing the failure, checking recent changes, tracing data flow, and validating single hypotheses before applying any fix. This systematic debugging process prevents repeated failed patches and symptom-fixing.

Debugging production incidents without guessing requires a four-phase process: root cause investigation, pattern analysis, hypothesis validation, and test-backed implementation. This approach insists on reproducing the issue and tracing data flow before proposing fixes.

Stop stacking patches by validating a single hypothesis at a time and escalating after repeated fix failures. Systematic debugging enforces stopping after failed attempts rather than applying more patches, ensuring you trace data flow to the actual root cause.

A failing test before fixing a bug verifies you have reproduced the root cause and protects against regressions after the solution is implemented. This testing-first repair approach confirms the fix resolves the actual issue without introducing new problems.

Systematic debugging applies to performance regressions, build failures, integration failures, and any ambiguous technical issue that tempts quick fixes. It diagnoses abnormal behavior by finding root causes through careful error inspection and pattern comparison.

Avoid quick workarounds when facing production incidents, flaky tests, or performance problems where a fix feels tempting but risky. Systematic debugging insists on root cause investigation through hypothesis testing and recent-change review before any implementation.