systematic-debugging

Test failures recur because symptom patching doesn't address the underlying root cause. You must complete evidence-based root cause investigation before proposing any fix to prevent wasted time and new bugs.

Debug race conditions using a four-phase workflow: root-cause investigation, pattern analysis, single-hypothesis testing, and implementation with a failing test to prevent incomplete understanding.

When production incident fixes fail, trigger a safety stop and return to Phase 1 root-cause investigation. Resist the quick patch temptation and pause to re-analyze evidence to ensure complete understanding.

Stop debugging unexpected behavior when you see specific danger signals, especially after multiple failed fixes. Return to root-cause investigation because most incomplete outcomes mean the investigation was insufficient.

Finding a root cause for environment or timing issues requires handling external factors carefully, while recognizing that most no root cause outcomes actually mean your root-cause investigation was incomplete.

Systematic debugging applies to performance, build, and integration failures by enforcing hypothesis testing and a failing test before implementation, ensuring fixes target evidence-based root causes.