Path: utzoo!mnetor!uunet!husc6!mailrus!umix!metavax!chris
From: chris@metavax.UUCP (Chris Collins )
Newsgroups: comp.software-eng
Subject: Re: American Programmer
Message-ID: <3169@metavax.UUCP>
Date: 12 Apr 88 13:57:38 GMT
References: <87@studsys.mu.edu> <3850007@wdl1.UUCP> <2350@uvacs.CS.VIRGINIA.EDU>
Reply-To: chris@metavax.UUCP (Chris Collins )
Organization: Meta Systems, Ltd. -- Ann Arbor, MI
Lines: 29

In article <2350@uvacs.CS.VIRGINIA.EDU> hsd@uvacs.cs.virginia.edu.UUCP (Harry S. Delugach) writes:
 
>What about short-sighted, "bottom-line" oriented company management which
>forbids you to "waste" time creating obviously non-functional comments,
>particularly if the project is perceived as easy or a 
>"one-shot deal". Later when the "one-shot" is revived or modified, 
>your new boss wonders why in the world you didn't forsee that it would
>be re-used. In such a case, it is often true that the real culprits
>(former managers) never have to face their mistakes.
>-- 
>Harry S. Delugach   University of Virginia, Dept. of Computer Science
>                    INTERNET: hsd@cs.virginia.edu
>                    UUCP: ..!uunet!virginia!uvacs!hsd
>                    BITNET: hsd2x@virginia

When management "forbids" you to do your job correctly, you have only a
couple of options: a) Look for other work immediately, and tell them
why on the spot.  Unfortunately I recognize that this is sometimes not
possible.  b) Tell them about the previous "one-shot" project that you
spent untold hours deciphering at unbelievable cost.  If you don't have
one make one up, or ask about on the net.  I'm sure many of us will gladly
donate such a horror story.  c) (my personal favorite) say, ok, and comment
the code anyway.

Somewhat humerous approach:  Remark that "non-functional comments" are
equivalent to "useful/intelligent managers".  (This could result in
option (a) above).

Chris Collins