debugging

Systematically debug software by enforcing a four-stage process: reproduce, locate, fix, and verify. This discipline prevents ad-hoc debugging by requiring evidence gathering, documentation, and non-guessing decision making to ensure reliable issue resolution.

To locate a root cause bug without guessing, trace the error origin using evidence, logs, and stepping through the call stack. Guardrails prevent skipping stages, enforcing non-guessing decision making and documentation during the locate phase.

To reliably reproduce a bug, create a minimal, deterministic test case that demonstrates the issue. The reproduce stage mandates documenting inputs, outputs, and decisions to establish a stable baseline before attempting to locate the root cause.

Yes, this systematic debugging workflow supports common frontend and backend scenarios. It applies evidence gathering, root cause tracing, and validation guardrails uniformly across both environments to ensure reliable issue resolution.

To verify a bug fix and prevent regressions, run original reproductions and the full test suite. The verify stage confirms the targeted root cause changes work correctly and ensures no regressions occur across the application.