systematic-debugging

To find the root cause of a test failure, follow a structured four-phase framework involving investigation, pattern analysis, hypothesis testing, and implementation to ensure evidence-based resolution.

The best way to debug production bugs systematically is to enforce evidence-based investigation and minimal hypothesis testing, preventing symptom-based patching and avoiding trial-and-error shortcuts.

Stop shotgun debugging by applying an anti-pattern detection process that explicitly identifies shortcuts and replaces them with architectural validation before proposing any code changes.

Use a systematic debugging framework when you are under pressure to resolve persistent test failures or production outages and are tempted to apply quick, unverified patches.

Verify a hypothesis before applying a patch by conducting minimal hypothesis testing during the dedicated testing phase, ensuring your fix targets the actual root cause rather than masking symptoms.

Symptom-based patching leads to new bugs because it bypasses evidence-based investigation and architectural validation, failing to resolve the actual root cause and introducing unverified code changes.