systematic-debugging

Systematic debugging is a structured investigation process that enforces root-cause analysis through evidence gathering and data-flow tracing before applying fixes, eliminating guesswork and reducing rework.

Debug flaky tests and production bugs by following a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation, using instrumented error reading and reproducibility to pinpoint failures.

Troubleshoot performance regressions by applying a multi-phase investigation that collects logs, reproduces failures, and traces data flow across components to identify the exact source before implementation.

Yes, you can use systematic debugging across any software issue including test failures and performance problems, as it requires no external dependencies and applies diagnostic instrumentation to guide evidence-driven resolution.

Debugging results in recurring fixes and firefighting when root-cause analysis is skipped; enforcing evidence collection and pattern analysis before implementation eliminates guesswork and resolves the underlying issue permanently.

You should not use systematic troubleshooting for trivial, immediately obvious errors where the root cause is already identified, as the four-phase investigation and evidence gathering process would unnecessarily slow down rapid fixes.