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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID 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: Richard D Riehle Subject: Re: Bugs or Mistakes? Date: 1999/11/13 Message-ID: <80kklc$p4n$1@nntp6.atl.mindspring.net>#1/1 X-Deja-AN: 548241935 References: <19991112202656.2368.rocketmail@web216.mail.yahoo.com> <1999Nov12.201602.1@eisner> <382DBE57.97B04F1E@callnetuk.com> Organization: MindSpring Enterprises X-Server-Date: 13 Nov 1999 21:19:40 GMT Newsgroups: comp.lang.ada Date: 1999-11-13T21:19:40+00:00 List-Id: In article <382DBE57.97B04F1E@callnetuk.com>, Nick Roberts wrote: >Occasionally, it is held, a bug would fall into the circuitry, causing >sporadic anomalous misbehaviour. Naturally, this became the simplest way >to explain any and all incorrect program behaviour to the (then utterly >clueless) management. Sometimes the "bug" is the manager who keeps you from getting the work done necessary to correct a problem, someone who bugs you until you do something even more extreme. Hickam AFB, circa 1967: A forty-eight bit word Honeywell 800 was an important part of the computer center. There was problem with it, clearly hardware-related. One Colonel kept interrrrrrrupting the technician, asking questions about the problem. Honeywell had to send in a tech rep from the U.S. Mainland to help solve it. He had been warned about the inquistive Colonel. "Well, Colonel, this is a sophisticated Honeywell 800 with a 48 bit word. Somehow a forty-ninth bit is showing up. We need to eradicate that 49th bit and everything will be OK." Long after the problem was fixed, the Colonel could be heard showing off his computer expertise by telling people about the 49th bit. Richard Riehle