systematic-debugging

To find a root cause before fixing a bug, follow an evidence-driven, four-phase workflow that prioritizes investigation, pattern analysis, hypothesis testing, and staged verification over symptom-focused patches.

The best way to debug production incidents without regressions is using a phased workflow that requires documented error analysis, reproducible steps, evidence tracing, and staged verification to ensure repairs address root causes.

To stop speculative fixes when debugging failing tests, apply anti-pattern defenses that explicitly guide you away from knee-jerk patches, rushing under pressure, and shortcuts, enforcing documented evidence tracing first.

Yes, a phased debugging workflow applies to both test failures and production incidents, guiding teams through root-cause investigation, pattern analysis, hypothesis testing, and fix implementation with multi-layer safeguards.

You should not use symptom-focused patches when rushing under pressure or facing complex failures; instead, use evidence-driven validation, trace data flow, and perform multi-layer checks to ensure robust repairs.

An evidence-driven debugging workflow involves four steps: investigate root causes, analyze patterns, form and test hypotheses, and implement fixes with safeguards, requiring documented error analysis and reproducible steps.