home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.org.eff.talk:8423 comp.software-eng:5247 misc.jobs.misc:8568
- Newsgroups: comp.org.eff.talk,comp.software-eng,misc.jobs.misc
- Path: sparky!uunet!wupost!csus.edu!netcom.com!lachman
- From: lachman@netcom.com (Hans Lachman)
- Subject: Re: Software as PE
- Message-ID: <1993Jan7.220546.12794@netcom.com>
- Organization: Netcom
- References: <1993Jan7.011056.10592@netcom.com> <C0Hu83.Gpp@ddsw1.mcs.com>
- Distribution: na
- Date: Thu, 7 Jan 1993 22:05:46 GMT
- Lines: 25
-
- In article <C0Hu83.Gpp@ddsw1.mcs.com> tcubed@ddsw1.mcs.com (James Hanlon) writes:
- >lachman@netcom.com (Hans Lachman) writes:
- >:
- >: I forgot one important point (and possibly others):
- >:
- >: - can handle or at least help with administrative tasks, such as
- >: project planning (estimating schedules, estimating manpower and
- >: equipment requirements), managing a bug-tracking database, and
- >: doing engineering-related paperwork (like patent applications)
- >:
- >With these sorts of talented engineers on the job, who needs managers?
- >Or do they realize that?
- >
- >James E. Hanlon, PE
-
- Are you sure you work in the real world? It's not unusual for managers
- to ask their engineers for their opinions on how long a project will
- take and how much manpower will be needed. The assumption is that
- the engineer can provide meaningful input (depending on his/her level
- of seniority).
-
- Is this not the case in other engineering fields?
-
- Hans Lachman
- lachman@netcom.com
-