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: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public From: drush@zakalwe.raleigh.ibm.com Subject: Re: What is wrong with OO ? Date: 1996/12/18 Message-ID: #1/1 X-Deja-AN: 204745256 references: <58aj6t$1ch@news3.digex.net> organization: ISSC South Region, RTP, NC 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." wrote in message <01bbec50$0abb3380$371883cc@beast.advancedsw.com> >[Comments about discarding prototype code snipped] >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. You are a unique manager. I have all too frequently been in the posisition of taking code that should have been tossed in the garbage as a basis for expanded functionality. In one case, we even had universal recognition from management that the code should have been tossed, but were directed to modify the prototype because the schedule wouldn't allow us to do it right. >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? Schedule according to engineering realities, not psychological needs. Educate clients about the hidden costs of doing a slap-dash design job. Shield engineers from clueless higher management. Etc... DeMarco and Lister (in Peopleware) got it pretty right, I think. The reasons why projects fail are rarely technical; they are usually organizational. david rush mailto:kumo@intercenter.net I bill $100/min for reading commercial E-mail.