systematic-debugging

Root cause analysis requires a systematic debugging process that enforces error reproduction, recent change verification, and evidence gathering before implementing fixes. This approach prevents recurring bugs by investigating the fundamental reason for the issue rather than applying quick patches.

Debugging a failing test in a CI/CD pipeline requires a structured approach: analyze error messages, reproduce the issue, check recent code changes, and gather evidence before proposing any fixes. This prevents unverified changes from introducing new issues into the pipeline.

Troubleshooting performance problems across multi-component systems requires systematic pattern analysis and hypothesis testing. By gathering evidence and identifying patterns across components, you can isolate the root cause and implement minimal targeted fixes rather than broad architectural changes.

A systematic debugging process should be used whenever you face bugs, test failures, performance problems, or build issues. It prevents architectural debt and wasted time by enforcing a four-phase approach: root cause investigation, pattern analysis, hypothesis testing, and minimal implementation.

Hypothesis verification during debugging requires testing your assumptions against gathered evidence and reproduced errors. The systematic process enforces hypothesis testing before implementation, ensuring fixes address the verified root cause rather than unconfirmed theories.

Systematic debugging works for build issues, test failures, performance problems, and unexpected behavior across multi-component systems. The four-phase process of error analysis, reproduction, evidence gathering, and minimal implementation applies universally to technical issue resolution.