Xref: utzoo comp.sw.components:357 comp.software-eng:2196 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!newstop!sun!coherent!mrspoc!itkin From: itkin@mrspoc.Transact.COM (Steven M. List) Newsgroups: comp.sw.components,comp.software-eng Subject: Re: Maintenance (was: Schedule and Budget...) Message-ID: <1989Oct18.170532.1586@mrspoc.Transact.COM> Date: 18 Oct 89 17:05:32 GMT References: <1271@accuvax.nwu.edu> Reply-To: itkin@guinan.Transact.COM Organization: Transact Software, Inc. Lines: 72 travis@delta.eecs.nwu.edu (Travis Marlatte) writes: >I don't see the reasoning that novice programmers should be given the >task of maintaining existing systems. I also don't see the reasoning that >thou who creates it will maintain it even unto ball and chain. This seems awfully absolute. I didn't hear anyone make either of these statements as absolutes. In fact, as regards the second statement, it was specifically mentioned as an option. There are MANY people who find the option to have responsibility for and commitment to a project from "womb to tomb" VERY attractive. There are others (myself included) who like to do a certain amount of work on a project and then move on to some- thing else. The threshhold varies, but the desire tends to be one for change and variety. >Simple analogy: A team of crack engineers build a beautiful and structurally >sound bridge that serves its purpose well. Five years after construction, >it is learned that the foundation at one end is giving way due to water >damage. The company assigns its newest employee to the task of designing >the correction to the problem. I notice that Travis said "newest employee", not "novice engineer" or "recent graduate." >Sounds absurd to me! I would hope it sounds absurd to the rest of you too. >Isn't the analogy correct. Why would I want to assign inexperienced staff >to the task of shoring up existing systems? Especially, since we know that >mainenance is often a task of stretching the intent of the original design >to meet current expectations. Further, why would I want my newest employee >dedicated to mastering 5 year old technology? Sounds absurd to me too. No one said that was the idea. The idea is that through working on fixing bugs (maybe major, maybe not), a new employee (not necessarily junior, however!!!!) can learn the systems, the techniques, and the standards and approach used by his/her new employer. While we tend to think of YOUNGER employees when we think of NEWER employees, this is CLEARLY not the case. When you change jobs, do you expect to walk into your new job and immediately start designing their hottest project? While it does happen, it is the exception rather than the rule. New employees have to learn their way around; socially, organizationally, and professionally. In our profession, this is frequently accomplished by putting the employee to work on low- to medium-priority maintenance tasks. > [ lots of interesting stuff about apprenticeship approaches ] I agree that apprenticeship is a terrific way to progress. Once again, I must point out that NEW employee does not translate to RECENT GRADUATE or YOUNG. Put the issue in perspective. >By the way, my first job out of school was as a maintenance programmer >for control systems. I didn't mind doing it but it certainly was a waste >of time. Only by becoming involved in curent design effort does one come >to understand the task of doing current design. "A waste of time." Does this let everyone know what Travis thinks of maintenance and programmers who DO maintenance? Obviously what is important and interesting to Travis is design and being in on the ground floor of a project. While that's true of many of us, we also learn to appreciate the time we get to work on maintenance. It can be a wonderful break from the pressure and pace of being at the front end. Like doing gardening or cooking or folding laundry. Like doing manual labor after programming all day. Change. Nurture versatility and an appreciation for ALL aspects of your profession, and you will BE a professional. -- +----------------------------------------------------------------------------+ : Steven List @ Transact Software, Inc. :^>~ : : Chairman, Unify User Group of Northern California : : {apple,coherent,limbo,mips,pyramid,ubvax}!itkin@guinan.Transact.COM :