PRINTABLE FIELD NOTES
Debugging methodology
Use this before an interview or during a focused review.
Debugging methodology
A strong diagnosis explains observations, predicts a test outcome and survives a counterexample.
| Scope | Define affected user journey, start time, frequency, geography, tenant and version. Capture sanitized request IDs. |
|---|---|
| Timeline | Align changes, metrics and failures. Correlation identifies candidates; it does not establish causality. |
| Compare | Choose a healthy control. Split request timing and identify the first divergent boundary. |
| Hypothesize | Write at least two plausible causes and a test that distinguishes them. Prefer safe, reversible experiments. |
| Mitigate | Restore customer outcomes while preserving evidence. Bound blast radius and name the rollback trigger. |
| Verify | Repeat the original failing journey plus controls. Monitor long enough to detect intermittent failure. |
| Learn | Document root cause, contributing conditions, corrective ownership and a regression test. Avoid blame and unsupported certainty. |