systematic-debugging

Systematically debug production outages and test failures by following a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This enforces root-cause discovery before applying fixes.

To stop applying symptom fixes during incident response, enforce phase-based debugging with explicit go/no-go rules and anti-pattern safeguards that resist time-pressure rationalization and shortcuts before implementation.

Conduct root-cause investigation for integration issues by completing Phase 1 of the debugging workflow before proposing any fixes, ensuring you analyze patterns and test hypotheses systematically across multiple layers.

You need defense-in-depth strategies during the implementation phase of bug fixing to add validations and robust defenses across multiple system layers, preventing future recurrences of the same root-cause defects.

Common debugging anti-patterns to avoid include skipping the root-cause investigation phase, taking shortcuts under time pressure, and applying symptom fixes without validating hypotheses or integrating defense-in-depth validations.