systematic-debugging

To debug a persistent production bug, use a systematic debugging framework that traces the root cause through a four-phase process: investigation, pattern analysis, hypothesis testing, and implementation, preventing ineffective symptom-based patching.

Troubleshoot a flaky test suite by applying anti-shortcut guardrails that block skipping tests, instead guiding you through evidence-based hypothesis testing and multi-layer defensive checks to isolate the actual root cause.

Symptom-based patching leads to recurring technical failures because it addresses superficial effects rather than the root cause, often introducing new bugs and wasting time when facing complex integration issues or system failures.

Trace data flow and add diagnostic instrumentation during the investigation and pattern analysis phases of systematic debugging, enabling evidence-based hypothesis testing to resolve complex integration issues.

Use systematic root-cause investigation instead of shotgun debugging when facing complex integration failures, production incidents, or flaky test suites where unstructured changes are ineffective and anti-shortcut guardrails are needed.