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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c8086456b887be55 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-04-27 19:53:20 PST Path: newsfeed.google.com!newsfeed.stanford.edu!headwall.stanford.edu!unlnews.unl.edu!newsfeed.ksu.edu!nntp.ksu.edu!news.okstate.edu!dvdeug From: dvdeug@x8b4e53cd.dhcp.okstate.edu (David Starner) Newsgroups: comp.lang.ada Subject: Re: Ada, Software Engineering and "weirdoes" (was License to Steal) Date: 27 Apr 2001 21:35:40 GMT Organization: Oklahoma State University Message-ID: <9cconc$8a21@news.cis.okstate.edu> References: <92HD6.3345$D4.334091@www.newsranger.com> <200104240531.WAA01552@well.com> <3AE5A34F.B89C8D5F@boeing.com> <9cbk4a$que$1@trog.dera.gov.uk> <3AE9B1F9.A9C2E8A4@boeing.com> Reply-To: dstarner98@aasaa.ofe.org NNTP-Posting-Host: x8b4e53d6.dhcp.okstate.edu User-Agent: slrn/0.9.7.0 (Linux) Xref: newsfeed.google.com comp.lang.ada:7007 Date: 2001-04-27T21:35:40+00:00 List-Id: On Fri, 27 Apr 2001, Jeffrey Carter wrote: > All the members of that sub-group received the MS SWSE, but that does > not make them software engineers. Their inability to implement a simple > piece of software in 15 weeks proves that they are coders. These were > people with several years experience in software development as well as > CS degrees. Clearly, neither education nor experience identify software > engineers. Saying coders = lousy programmers and software engineers = good programmers is not a useful distinction, and it's somewhat arrogant to boot. If making the distinction between a software programmer and an software engineer is useful and meaningful, it has to do with the design of code, not the speed of implementation. That you could code their problem in 4 hours is not interesting. Was your code documented? Was it maintainable? Did it follow a clear design plan? Were the same style conventions used throughout the code? Was it tested? Did it have a formal test structure? Many a programmer who couldn't write structured, maintainable code to save his life can churn out working (for common cases) code extremely fast. -- David Starner - dstarner98@aasaa.ofe.org Pointless website: http://dvdeug.dhis.org "I don't care if Bill personally has my name and reads my email and laughs at me. In fact, I'd be rather honored." - Joseph_Greg