systematic-debugging

Systematic debugging is a rigorous four-phase framework for resolving technical issues. You need it when facing software debugging, test failure analysis, or system performance troubleshooting to identify root causes rather than applying superficial symptom-based patching.

To trace a test failure, apply the four-phase framework of investigation, pattern analysis, hypothesis testing, and implementation. This enforces evidence-based hypothesis testing and architectural validation to find the original trigger instead of using random patches.

The best way to stop recurring bugs is using anti-shortcut guardrails that prevent rationalizations like adding quick fixes. This enforces evidence-based hypothesis testing and architectural validation to eliminate symptom-masking fixes and technical debt.

Yes, you can use this framework for production API failures. It applies to software debugging, test failure analysis, and system performance troubleshooting, tracing errors back to their original trigger rather than applying superficial workarounds.

To prevent symptom-based patching when in a hurry, the framework explicitly identifies and blocks common rationalizations like being in a hurry. It requires adherence to systematic investigation and evidence-based hypothesis testing to ensure proper root cause resolution.