home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!mole-end!mat
- From: mat@mole-end.matawan.nj.us
- Subject: Re: Will we keep ignoring this productivity issue?
- Message-ID: <1992Nov16.090509.22236@mole-end.matawan.nj.us>
- Summary: Engineers managed by engineers, programmers by programmers
- Organization: :
- References: <1776@aviary.Stars.Reston.Unisys.COM> <1992Nov11.055130@eklektix.com> <BxpLGC.DCp@cs.uiuc.edu>
- Date: Mon, 16 Nov 1992 09:05:09 GMT
- Lines: 26
-
- In article <BxpLGC.DCp@cs.uiuc.edu>, johnson@cs.uiuc.edu (Ralph Johnson) writes:
- > rcd@raven.eklektix.com (Dick Dunn) writes:
-
- > >I'm honestly not sure...is this a lesson for software engineering, that we
- > >have to assume anybody good enough will get shipped out? Or is it a lesson
- > >for management, that they seem reluctant to learn?
-
- > ... One of the problems with software development is that the managers don't
- > know enough about software to tell who are the stellar performers and who
- > are the duds. Thus, the strategy "just hire very good people" can't work
- > because it can't be implemented: management is not able to tell who is
- > good and who is not.
-
- > ... I never have any trouble telling which of my students are good
- > programmers: I read their code. In my opinion, managers should look at
- > what their employees are doing to see if they are doing a good job or not.
- > In the case of software engineers, that means reading design documents,
- > programs, test suites, and anything else they produce.
-
- In other words, the manager has to have an appreciation of the `useful
- art' of programming! Which means they have to be good programmers themselves.
- --
- (This man's opinions are his own.)
- From mole-end Mark Terribile
-
- mat@mole-end.matawan.nj.us, Somewhere in Matawan, NJ
-