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: f43e6,d3d1abbae7094b87 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,d3d1abbae7094b87 X-Google-Attributes: gid103376,public From: dick@silicon.csci.csusb.edu (Dr. Richard Botting) Subject: Re: Three releases and rewrite? Date: 1996/08/15 Message-ID: <4uvm3r$ave@news.csus.edu>#1/1 X-Deja-AN: 174754769 references: <4utj8s$14q@su102w.ess.harris.com> followup-to: comp.software-eng,comp.lang.ada organization: CS Dept., Calif. State Univ., San Bernardino newsgroups: comp.software-eng,comp.lang.ada Date: 1996-08-15T00:00:00+00:00 List-Id: Scott McCoy (smccoy@hisd.harris.com) wrote: : General question: In the recent past, as my group has gotten more and : more away from pure DoD development and more into non-government work, : I've noticed something: : It seems like a rule of thumb for commercial software applications : is that after three major releases (i.e., 1.0, 2.0, 3.0), you : rewrite the application from scratch. [...] : Is this a reasonable rule of thumb? This may be rather like Brookes's observations. My own rule is to never buy an even numbered release. : ON HUMILITY : To err is human, to moo bovine. To err is human, but to really foul things up, make it into a law or program. -- dick botting http://www.csci.csusb.edu/dick/signature.html Disclaimer: CSUSB may or may not agree with this message. Copyright(1996): Copy freely but say where it came from. I have nothing to sell, and I'm giving it away.