From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,de5dfd6df880dd3 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Bugs or Mistakes? Date: 1999/11/13 Message-ID: <1999Nov12.201602.1@eisner>#1/1 X-Deja-AN: 547980755 References: <19991112202656.2368.rocketmail@web216.mail.yahoo.com> X-Trace: news.decus.org 942455769 20549 KILGALLEN [216.44.122.34] Organization: LJK Software Reply-To: Kilgallen@eisner.decus.org.nospam Newsgroups: comp.lang.ada Date: 1999-11-13T00:00:00+00:00 List-Id: In article <19991112202656.2368.rocketmail@web216.mail.yahoo.com>, MaryAnn Atkinson writes: > Richard D Riehle wrote: > >> What we call a "bug" is actually a mistake. Someone tried to do >> something and made a mistake. The mistake results in a defect. >> The defect is a potential run-time fault. Managers need to take >> the responsibility for elminating the word "bug" from the >> vocabulary of their software personnel. > > Why so harsh words? You are talking about a "bug" like its > a dirty word, or like we are somehow not allowed to make them... > > Bugs are mistakes ONLY if they are not found and corrected! What exists in the software is a defect. A mistake might be the action that introduced the defect, but since defects are often due to sins of omission rather than sins of commission, looking for the occasion on which the "mistake" was made might be difficult. Of course not all defects deserve to be fixed, especially since the fix often will destabilize the resulting software. My experience has been that organizations with the guts to use the term "defect" have a better chance at good quality control. Your mileage may vary. Larry Kilgallen