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, and only then form a hypothesis and test it with a minimal change.

Root cause analysis identifies why a bug occurs rather than patching its symptoms. It involves reproducing the issue, gathering evidence at component boundaries, and tracing bad values upstream to their origin before implementing any fix.

After three failed fix attempts, stop and question the architecture. Signs include each fix revealing new coupling elsewhere, fixes requiring massive refactoring, or new symptoms appearing after every change.

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

Yes, systematic debugging is faster than guess-and-check thrashing even in emergencies. A structured investigation typically resolves issues in 15-30 minutes versus hours of random fix attempts with low first-time success rates.