Chapter 22. Handling Defects
Report 'em, schedule 'em, test and fix 'em, avoid 'em. Just don't call 'em bugs.
Call them Incident Reports or Customer Information Requests if you like. Just don't call them bugs. Bugs are things that creep into your software against your will. Every defect in your code was put there by one of the programmers. Two of the programmers, with pair programming. With the customers we visit, when something goes wrong, they think it's a defect. We'll talk here about reporting the problem, scheduling the repair, testing and fixing the problem, and avoiding as many defects as possible. But first, a word from our sponsor. ...
Get Extreme Programming Installed 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.
