Chapter 6Discovering That You Have a Problem
In the first part of the book, we started from the point at which we already knew that we had a bug. In this chapter, we’ll look at what comes before this.
Bugs can come to light at any point in the software development cycle—from seconds after the code is written to months or years after it’s released. Ideally, you’ll find them yourself and as early as possible—it’s easier to fix bugs that are detected quickly, and doing so avoids the embarrassment (or worse) of allowing a bug to escape into the wild.
Nevertheless, there will be occasions where, despite your best efforts, a customer is affected by a bug. In this chapter, we’ll talk about what happens after they have been. Specifically, we’ll ...
Get Debug It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
