systematic-debugging

To identify a root cause, apply a four-phase systematic debugging workflow that gathers evidence using terminal commands, file searches, and git history to test hypotheses and verify the fix before implementation.

The best way to debug test failures is to use a systematic debugging process that investigates patterns, tests hypotheses against gathered evidence, and verifies the implemented fix to prevent regressions.

You investigate production crashes and performance issues by executing terminal commands, reading files, and searching version-control history to collect evidence, analyze patterns, and confirm your hypothesis.

Yes, you can search version-control history, such as git, to gather evidence for integration problems, which helps test hypotheses and verify the root cause during the systematic debugging workflow.

Yes, systematic debugging applies to performance bottlenecks, production crashes, test failures, and integration errors by guiding investigation, pattern analysis, hypothesis testing, and verified implementation across all scenarios.

Superficial fixes lead to technical debt because they apply changes without understanding why code fails, causing regressions; a systematic root-cause debugging process prevents this by verifying fixes against gathered evidence.