systematic-debugging

To find the root cause of test failures, you must complete a systematic investigation phase before proposing any fixes. This approach enforces pattern analysis and single hypothesis testing to prevent wasted time and new bugs from superficial symptom patching.

The best way to debug flaky tests and unexpected production breakages is a four-phase workflow: Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It includes anti-shortcut guardrails to resist quick fixes under time pressure and mandates creating a failing test case before implementation.

When your debugging hypothesis fails to fix a code issue, you should stop and re-analyze the problem to form a new single hypothesis. If repeated attempts fail, the process requires escalating to architecture questions to challenge underlying structural assumptions.

To trace bugs backward through call stacks for integration failures, apply deep debugging techniques that systematically track execution flow. This process ensures you validate a single hypothesis with minimal testing and add defense-in-depth validations across layers before applying final code fixes.

Yes, you can apply systematic debugging to performance issues and build errors under time pressure. The workflow includes explicit red flags and anti-patterns to resist time-pressure rationalizations, ensuring you still complete root-cause investigation before attempting any quick fixes.