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: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: 11cae8,b87849933931bc93 X-Google-Attributes: gid11cae8,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public From: ameyer@ix.netcom.com (Alan Meyer) Subject: Re: What is wrong with OO ? Date: 1996/12/11 Message-ID: <58mubr$imj@sjx-ixn10.ix.netcom.com>#1/1 X-Deja-AN: 203535036 references: <32A4659D.347A@shef.ac.uk> <32a5ceba.81462731@news.nstn.ca> <32A885CF.5530@csn.net> <32a98036.46416970@news.nstn.ca> <58lbbo$8kl@news.xmission.com> content-type: Text/Plain; charset=US-ASCII organization: AM Systems x-netcom-date: Wed Dec 11 10:26:03 AM PST 1996 mime-version: 1.0 newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.lnag.java,comp.object,comp.software-eng Date: 1996-12-11T10:26:03-08:00 List-Id: In article <58lbbo$8kl@news.xmission.com>, tknarr@xmission.com wrote... <> >All too often, though, the "systems analysts" hand me a design document >which I'm supposed to implement which is exactly the programming >equivalent of that 1000-foot single-span stone bridge. I once visited a large municipal government computing shop with 130 people working there. I was told by the boss that as far as he's concerned, his "systems analysts" are to do all the thinking and his programmers, he called them "coders", are just supposed to translate those lofty thoughts into code. He then thought that the reason the average programmer only stayed 18 months (remember that's the average, I wonder what the good ones were doing!) was because that was the nature of the business and programmers were defective people anyway! I personally believe that the division into "analysts" and "programmers" is a dangerous one. If a person can't do both he is likely to do a lot of harm to a project. An "analyst" that doesn't understand programming will often specify impractical designs. A "programmer" that can't understand the needs of the users will often build unusable programs. The best systems always come from people who make it their business to understand the total problem from the point of view of the user, the point of the view of the machine, and everything in between.