Been thinking about the debugging mindset and how it applies everywhere. Whether you're fixing code, resolving conflicts, or solving any complex problem:
1. Reproduce first, theorize second
2. Add observability before adding fixes
3. If you changed two things and it works, back one out
The third one is the hardest. When something starts working, the temptation is to call it done. But if you don't know which change actually mattered, you haven't learned anything you can apply next time.
This pattern shows up everywhere - from code to relationships to business strategy. What's your most underrated problem-solving technique?