Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: $Revision: 1.6.2.13 $; site uiucdcs.UUCP Path: utzoo!linus!vaxine!wjh12!genrad!decvax!ucbvax!ucbcad!tektronix!uw-beaver!cornell!vax135!houxz!houxm!ihnp4!inuxc!pur-ee!uiucdcs!liberte From: liberte@uiucdcs.UUCP Newsgroups: net.lang Subject: Re: Batch Programming / Re: ..., Going O - (nf) Message-ID: <26400013@uiucdcs.UUCP> Date: Mon, 2-Jul-84 00:13:00 EDT Article-I.D.: uiucdcs.26400013 Posted: Mon Jul 2 00:13:00 1984 Date-Received: Thu, 21-Jun-84 01:38:56 EDT References: <3572@fortune.UUCP> Lines: 25 Nf-ID: #R:fortune:-357200:uiucdcs:26400013:000:1026 Nf-From: uiucdcs!liberte Jun 17 23:13:00 1984 #R:fortune:-357200:uiucdcs:26400013:000:1026 uiucdcs!liberte Jun 17 23:13:00 1984 /**** uiucdcs:net.lang / gurr@west44 / 11:14 pm Jun 13, 1984 ****/ > ... You > should never be proud when you track down a bug in your > own program. It's like finding a cockroach in your > kitchen. You should be embarrassed and upset that it was > there in the first place. This philosophy is *dangerous*. ... Dave Gurr, Westfield College, Univ. of London, England. /* ---------- */ I quite agree. Although I am somewhat embarrassed and upset at the existence of a bug - more upset when it is not my bug - I am learning to take it in stride. However, I am proud and cheered to find the bugger, and I believe rightfully so. It is good work to fix things, no matter why they are busted. An important part of debugging is to track down why the bug exists - sniff out the crummy code - exclaim "pay dirt!" and clean up the mess. Easier said than done. Daniel LaLiberte (ihnp4!uiucdcs!liberte) U of Illinois, Urbana-Champaign, Computer Science {moderation in all things - including moderation}