[Top] [All Lists]

[TenTec] Orion 1st Year of Use

To: tentec@contesting.com
Subject: [TenTec] Orion 1st Year of Use
From: Don Rasmussen <wb8yqj@yahoo.com>
Reply-to: Discussion of Ten-Tec Equipment <tentec@contesting.com>
Date: Wed, 1 Jun 2005 13:50:14 -0700 (PDT)
List-post: <mailto:tentec@contesting.com>
<snip>Debugging is twice as hard as writing the code
in the first  place. Therefore, if you write the code
as cleverly as possible, you  are, by definition, not
smart enough to debug it. (reprint)<snip>  

>>>>> Here is another one I gathered. I didn't write
it, it's obviously no more true of Orion than any
other software project. Read, laugh, enjoy...

Software development cycle:
1.  Programmer produces code he believes is bug-free.
2.  Product is tested. 20 bugs are found.
3.  Programmer fixes 10 of the bugs and explains to
the testing department that the other 10 aren't really
4.  Testing department finds that five of the fixes
don't work and discovers 15 new bugs.
5.  Repeat three times steps 3 and 4.
6.  Due to marketing pressure and an extremely
premature product announcement based on
overly-optimistic programming schedule, the product is
7.  Users find 137 new bugs.
8.  Original programmer, having cashed his royalty
check, is nowhere to be found.
9.  Newly-assembled programming team fixes almost all
of the 137 bugs, but introduce 456 new ones.
10.  Original programmer sends underpaid testing
department a postcard from Fiji.  Entire testing
department quits.
11.  Company is bought in a hostile takeover by
competitor using profits from their latest release,
which had 783 bugs.
12.  New CEO is brought in by board of directors. He
hires a programmer to redo the program from scratch.
13.  Programmer produces code he believes is bug-free.

Discover Yahoo! 
Get on-the-go sports scores, stock quotes, news and more. Check it out! 
TenTec mailing list

<Prev in Thread] Current Thread [Next in Thread>