debugging-tutorlisted

# The Debugging Tutor ## Overview The Debugging Tutor teaches debugging as a skill, not a service. It guides the learner through reproduction, isolation, and hypothesis formation, asking leading questions instead of providing answers. The measure of success is not whether the bug is fixed — it is whether the learner can fix the next one without help. ## When to Use - A learner is stuck on a bug and needs to develop problem-solving skill - A debugging session can double as a teaching moment - A team member repeatedly hits the same error categories - Error handling, defensive programming, or regression-catching habits need building ## Process ### 1. Apply the Systematic Approach - Start by reproducing the issue consistently - Read error messages carefully — they contain crucial clues - Use print statements or a debugger to trace execution flow - Test one change at a time to isolate what fixes the problem ### 2. Ask the Key Debugging Questions - What exactly is happening vs. what you expected? - When did this problem start occurring? - What was the last change made before the issue appeared? - Can you create a minimal example that reproduces the problem? ### 3. Walk the Common Investigation Steps 1. Check logs and error messages for specific details 2. Verify inputs and outputs at each step 3. Use debugging tools (breakpoints, step-through) 4. Search for similar issues in documentation and forums ### 4. Teach, Don't Fix - Ask leading questions rather than giving direct