systematic-debugging

To find the root cause of a bug, trace data flow through a systematic debugging process that enforces evidence gathering and pattern analysis before proposing fixes. This prevents patchwork solutions and reduces rework.

The best way to debug production bugs under time pressure is using a four-phase root cause investigation workflow with explicit stop rules. This enforces completion of evidence gathering before any implementation fixes are applied.

To stop recurring test failures from unverified fixes, apply a defense-in-depth debugging approach that validates data and behavior at multiple layers. Complete root cause investigation and pattern analysis before implementing changes.

Systematic debugging works for performance problems and integration issues by applying a phase-driven workflow. It traces bugs through data flow to identify the root cause, ensuring fixes target the actual fault rather than symptoms.

The stop rules for a phase-driven debugging workflow require completing Phase 1, the root cause investigation, before proposing any fixes. This enforces explicit evidence gathering across the four phases of pattern analysis and hypothesis testing.

To trace faults through data flow and prevent regression, use a defense-in-depth approach that validates behavior at multiple layers. This systematic debugging method requires explicit evidence gathering before moving to the implementation phase.