Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!emory!hubcap!ncrcae!ncrlnk!ncrcce!mercer
From: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
Newsgroups: comp.unix.wizards
Subject: Re: The *ART* of Computer Programming
Message-ID: <1953@ncrcce.StPaul.NCR.COM>
Date: 6 Mar 90 20:56:15 GMT
References: <1990Feb26.234217.23251@aucs.uucp> <732@sppy00.UUCP> <25eb63c7.6a42@polyslo.CalPoly.EDU> <12533@nigel.udel.EDU> <1990Mar2.184550.5037@oracle.com> <7858@tank.uchicago.edu>
Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)
Organization: NCR Comten, Inc.
Lines: 32
Keywords:

In article <7858@tank.uchicago.edu> matt@group-w.uchicago.edu (Matt Crawford) writes:
:) >Have you never heard of a one-time program? 
:) 
:) I have heard of them, certainly.  I have just never seen one.
:
:I saw one, one time.  So I'm sure I'll never see another ...

Gee,  I probably write 10-20 a month.  Most don't do much of anything
and are purely of an educational nature (after 10 years in this business,
I have learned a 'Show Me' attitude towards documentation.  I've
found more than my share of discrepancies between the way something
works and the way the doco says it works).  I also write a lot of
one shot awk programs.  Since those programs are written inside of
vi then !awk  'ed,  they don't even survive the editing session.

However,  that's only a quibble.  Years ago I hacked up a couple of
one shots that were only gonna last as long as a quick demo to my boss.
Inelegantly coded,  uncommented and undocumented.  And still in use.
With new additions hammered on at intervals.  Impossible to support,
impossible for even me to understand any more.  Worse,  I've had 
requests for them,  but I'm too ashamed to hand them out (people
would think me MAD!!!HA!HA!HA!).  Not that they'd even be portable.

So my rule of thumb is,  if you don't intend to erase the file as soon
as you're done,  do it up right the first time.

Course,  I break the rule all the time.

-- 

Dan Mercer
Reply-To: mercer@ncrcce.StPaul.NCR.COM (Dan Mercer)