debugging-and-error-recovery

Systematic debugging is a structured triage process to identify and isolate the root cause of failures. It helps teams avoid guessing and reduces mean time to resolution by preserving evidence and following a stepwise checklist.

Debug test failures, build errors, and runtime bugs by applying a triage checklist: reproduce, localize, reduce, repair, guard, and verify. This stepwise process guides you from initial failure reproduction to final fix verification.

Handling a production incident requires a stop-the-line rule to halt feature changes, preserving evidence immediately, and diagnosing the root cause via triage before resuming work to prevent compounding errors.

Yes, structured triage applies to test failures, build errors, runtime bugs, and production incidents. It enforces evidence preservation and a stepwise diagnostic checklist to repair and guard against both development and production failures.

You should stop adding features when a build error or test failure is detected to prevent compounding issues. This stop-the-line rule ensures you preserve evidence and focus on diagnosing the root cause before resuming work.