systematic-debugging

Finding the root cause of test failures requires enforcing a structured investigation before applying any fixes. You must complete four phases: root cause investigation, pattern analysis, hypothesis testing, and implementation, ensuring no changes are made without full understanding.

To stop applying quick fixes that introduce new bugs, follow an anti-shortcut defense mechanism that halts development when understanding is incomplete. You must recognize rationalizations as red flags, stop immediately, and return to initial root cause investigation before proceeding.

Debugging failures across multi-layer systems involves gathering evidence across component boundaries and tracing data flow backward through the call stack. This systematic approach ensures you accurately identify the exact point of failure before forming any hypotheses.

Debugging code under time pressure requires resisting the temptation of a quick fix and adhering to a pressure-resistant workflow. You must still complete all four investigation phases sequentially, stopping to re-analyze whenever a proposed fix fails or your understanding remains incomplete.

You should write a failing test during the hypothesis and testing phase, specifically before beginning the implementation phase. This ensures your proposed fix is validated against the actual failure condition, confirming the root cause is resolved before the code is changed.