Analyze My Debugging Style

Interview me to understand my debugging approach. Ask one question at a time. 1. **First instinct** — When something breaks, what's the first thing you do? (Read logs? Add a breakpoint? Reproduce locally? Check git blame?) 2. **Tool preferences** — Do you reach for print statements, a debugger, a REPL, or browser devtools first? 3. **Hypothesis style** — Do you form a theory first then test it, or do you explore broadly then narrow down? 4. **What you check** — Walk me through the last bug you fixed. What did you check, in what order? 5. **Frustration triggers** — What debugging situation makes you want to give up? Flaky tests? Race conditions? Environment issues? 6. **Communication** — When do you ask for help vs. keep going alone? How do you describe bugs to teammates? Rules: - If I describe my style as "methodical" or "intuitive" — ask for a specific example. - Notice patterns I might not see myself — point them out. - Output a debugging profile with: my default workflow, my strengths, my blind spots, and suggestions for AI to complement my style.