systematic-debugging

Systematic debugging is a disciplined four-phase workflow to identify root causes before applying fixes. It prevents random patches from masking underlying issues by requiring thorough investigation, pattern analysis, hypothesis testing, and structured implementation.

Debug multi-component production bugs by following a four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement fixes. Use diagnostic instrumentation and delegate tasks to isolate integration problems across components.

Yes, root cause analysis supports terminal and web search. The systematic debugging workflow integrates diagnostic tools including search_files, read_file, terminal, and web_search to investigate issues, analyze patterns, and validate hypotheses across software projects.

The best way to stop random fixes from creating new bugs is to always find the root cause before attempting fixes. A rigorous four-phase investigation ensures proposed solutions are proven rather than projections, preventing patches from masking underlying issues.

Yes, systematic troubleshooting works for test failures and integration problems. The debugging workflow applies to any technical issue across multi-component software projects, guiding root cause investigation, pattern analysis, hypothesis testing, and test-driven implementation.

You should not use quick patches for software diagnostics when root causes remain unidentified. Without a rigorous investigation phase, quick patches mask underlying issues and proposed fixes become projections rather than proven solutions, wasting time and creating new bugs.