systematic-debugging

Fix recurring technical bugs by enforcing a four-phase root cause investigation workflow before proposing any changes. This prevents wasted time and thrashing by requiring pattern analysis and hypothesis testing to resolve the underlying issue.

Debug flaky tests and CI build failures systematically by forming a single hypothesis with minimal tests, creating a failing test for the root-cause fix, and stopping to re-analyze architecture after multiple failed fixes.

Debugging production incidents thrashes because guessing fixes without root cause investigation leads to wasted effort and recurring bugs. Disciplined hypothesis testing and pattern analysis are required to stop the cycle.

Carry out root cause analysis for unexpected behavior by completing four phases: root cause investigation, pattern analysis, hypothesis with testing, and implementation, ensuring disciplined analysis before any code changes.

During incident response, stop trying fixes and re-analyze architecture when multiple fixes fail, triggering explicit red flags and escalation to prevent further thrashing and wasted time.

Systematic debugging works for integration problems and performance issues by applying a disciplined four-phase workflow with anti-rationalization guardrails to any technical failure scenario, including build and integration problems.