Xref: utzoo comp.sw.components:325 comp.software-eng:2143 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!cmcl2!lanl!opus!ted From: ted@nmsu.edu (Ted Dunning) Newsgroups: comp.sw.components,comp.software-eng Subject: Re: Schedule and budget are secondary Message-ID: Date: 12 Oct 89 16:41:43 GMT References: <16168@vail.ICO.ISC.COM> <6693@hubcap.clemson.edu> <16187@vail.ICO.ISC.COM> <3807@rtech.rtech.com> Sender: news@nmsu.edu Followup-To: comp.sw.components Organization: NMSU Computer Science Lines: 36 In-reply-to: linda@rtech.rtech.com's message of 11 Oct 89 22:49:07 GMT In article <3807@rtech.rtech.com> linda@rtech.rtech.com (Linda Mundy) writes: In article <16187@vail.ICO.ISC.COM> rcd@ico.ISC.COM (Dick Dunn) writes: ... I personally think that any new, just-out-of-school programmer should do maintenance work for awhile (assuming, of course, that the company already has a product!) ... why wait until then? one of the most important things that any course in software engineering should have students do is work on a large system. for that matter, so should _all_ but the most basic courses. if you have compiler class, make them work on a real compiler, in a course on semantics, make them work with the semantics of a real language. ... But the most important point: don't diminish people because of their relative positions. It can't do any good -- in fact, it is exactly such attitudes that lead to "bored, second-string" employees -- wherever they happen to be in the organizational structure. ... i am not sure that dick was trying to diminish people asmuch as he was just observing that the programmers who do maintenance and typically _are_ bored, typically _are_ second-string. -- ted@nmsu.edu Dem Dichter war so wohl daheime In Schildas teurem Eichenhain! Dort wob ich meine zarten Reime Aus Veilchenduft und Mondenschein