systematic-debugging

Systematic debugging is a disciplined four-phase workflow enforcing root cause investigation before code changes. It prevents symptom-focused fixes by requiring data-flow tracing and multi-layer validation to resolve production incidents and flaky tests.

To find the root cause of a flaky test, start with Phase 1 Root Cause Investigation before making fixes. Trace data flow across codebase layers to identify patterns, then form and test hypotheses before implementing the actual code changes.

The best way to debug production incidents under time pressure is applying a phased debugging workflow. Complete root cause investigation first, analyze patterns, test hypotheses, and implement defense-in-depth validation across layers to ensure rushed fixes do not fail.

Yes, this debugging workflow is applicable to any bug, test failure, or unexpected behavior across codebases and CI pipelines. It enforces a structured four-phase process regardless of the specific technology stack or project scale.

Yes, you can use defense-in-depth validation during root cause analysis. The debugging workflow encourages multi-layer validation and data-flow tracing to effectively catch edge cases and ensure comprehensive bug resolution across system layers.

You should not use quick fixes for unexpected behavior in CI pipelines when time pressure tempts rushed patches. Avoid symptom-focused fixes by completing Phase 1 root cause investigation and tracing data flow before implementing any code changes.