This document discusses techniques for debugging code including describing the problem in detail, reproducing the problem, reducing the problem to its essential parts, using logging, the debugger, test cases, verifying assumptions, intentionally breaking the code, reading compiler errors, and making one modification at a time. It emphasizes collecting useful information in bug reports such as steps to reproduce, when the issue started occurring, and frequency.

1. Debugging
RailsGirls DC 2012
Brock Wilcox
awwaiid@thelackthereof.org

3. Debugging
Troubleshooting
Problem Solving
Detective Work

4. Describe the problem

5. Good bug reports collect these:
• What are you trying to achieve?
• Is this one issue or many?
• Is this a code issue?
• When did the issue start?
• How often does it occur?
• Is it reliably reproducable?
• Are there test-steps?
• Screenshot / Screencast?
• Is there a work-around?

6. Reproduce the Problem

7. Reduce the Problem

8. Logging
(warn "Here!")

9. Debugger

10. Test Case

11. Verify Assumptions

12. puts "right now person is set to:", person

13. Break It!

14. Compiler help
(Read the Error Message)

15. One modification at a time

16. Never fix again

17. THE END