The document discusses how to fix bugs in software programs or systems. It defines what a bug is and outlines four key steps to fixing bugs: 1) understanding the application where the bug lives, 2) having a reliable way to reproduce the bug, 3) finding the specific line of code causing the bug, and 4) being able to make changes or add debugging information without disrupting production services.

1. “ How To Fix Bugs” Mike Peters, Software Projects Inc.

2. My name is Mike Peters .

3. What is a “ bug ”?

4. …” the common term used to describe an error, flaw, mistake, failure , or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design ...” - Wikipedia

5. Bugs are bad.

6. What do we need before we can Fix Bugs ?

7. 1. Understanding the app where the bug lives 2. A reliable “ how to reproduce ” path 3. The line or block of code causing the bug 4. A way to make changes / add debug info, without disrupting any production services

11. Applying “ binary sort ” to pinpoint the line / block causing our bug

15. 4. Make changes / add debug info, without disrupting any production services Find if this is a Design , Code or Third-party issue?

17. Questions?