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=2.1 required=5.0 tests=BAYES_40,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public From: mbk@caffeine.engr.utk.edu (Matt Kennel) Subject: Re: What is wrong with OO ? Date: 1996/12/18 Message-ID: <599fak$l5v@gaia.ns.utk.edu>#1/1 X-Deja-AN: 204774927 references: <58aj6t$1ch@news3.digex.net> <01bbeb6f$e2220c40$371883cc@beast.advancedsw.com> <01bbec50$0abb3380$371883cc@beast.advancedsw.com> followup-to: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng organization: University of Tennessee, Knoxville and Oak Ridge National Laboratory reply-to: %%spam repellent: remove this prefix%%kennel@msr.epm.ornl.gov newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng Date: 1996-12-18T00:00:00+00:00 List-Id: Roger T. (roger@advancedsw.com) wrote: : This brings up a succeeding issue. : Let's assume that coders are given the freedom to discard their prototypes. : The next problem facing me as a manager is to make sure they actually use : that freedom. : The desire to paste functionality onto the prototypes to "fix" them so they : support new functionality is very seductive when it means a short term time : savings. To some extent you are re-inventing the wheel, though in a better : form. : Designers must realize that prototype extinction is not only allowed but is : encouraged if it has the effect of creating long term product robustness. : How would you encourage/enforce that philosophy with your developers? Perhaps I am naive, but what about asking them? "How much of the prototype did you keep? Was it good enough to keep or do you wish you would have time to re-do it from scratch? Don't assume I wouldn't have let you." : Roger T. -- Matthew B. Kennel/mbk@caffeine.engr.utk.edu/I do not speak for ORNL, DOE or UT Oak Ridge National Laboratory/University of Tennessee, Knoxville, TN USA/