systematic-debugging

Start by reading the full error message and stack trace, then reproduce the failure consistently with a command like pytest -v. Check recent git changes, trace the data flow to the source of the bad value, and only then form a hypothesis and test it with a minimal change.

Root cause analysis means identifying why a bug occurs before fixing it, rather than patching symptoms. It involves reproducing the issue, gathering evidence at component boundaries, and tracing bad values upstream to their origin.

Stop after three failed fix attempts. If each fix reveals new coupling or creates symptoms elsewhere, the pattern itself is likely flawed. Discuss refactoring the architecture with your team instead of attempting a fourth fix.

Quick fixes address symptoms without understanding the underlying cause, so the real problem persists and the patch often introduces new defects. Bundling multiple changes also makes it impossible to isolate what actually worked.

Yes, and it is especially valuable during emergencies. A structured investigation typically resolves issues in 15-30 minutes, while random guess-and-check attempts often consume hours and introduce regressions.