systematic-debugging

Find root cause before fixing. Never skip root cause investigation.

• Four-phase framework for systematic debugging
• Root cause investigation before any fix
• Scientific method: hypothesize, test, verify
• Root cause fixes, not symptom fixes

• NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
• MUST complete each phase sequentially
• Trace data flow to find origin of bad value
• Form single hypothesis and test minimally
• If 3+ fixes fail, question architecture
• Always verify fix works before moving on
• Gather evidence across component boundaries
• Never skip root cause in emergencies

1. 1.Complete Phase 1: investigate root cause thoroughly
2. 2.Phase 2: analyze patterns and differences between working/broken cases
3. 3.Phase 3: form hypothesis and test with minimal change
4. 4.Phase 4: implement fix, verify, and validate resolution
5. 5.If 3+ fixes fail, stop and question architecture
6. 6.Always document and verify before moving to next phase