Xref: utzoo comp.software-eng:2459 comp.misc:7427 Path: utzoo!attcan!uunet!samsung!gem.mps.ohio-state.edu!usc!apple!sun-barr!newstop!sun!looney!dopey From: dopey%looney@Sun.COM (Can't ya tell by the name) Newsgroups: comp.software-eng,comp.misc Subject: Re: Programmer productivity Message-ID: <128179@sun.Eng.Sun.COM> Date: 21 Nov 89 03:15:57 GMT References: <34796@regenmeister.uucp> <2226@jato.Jpl.Nasa.Gov> Sender: news@sun.Eng.Sun.COM Reply-To: dopey@sun.UUCP (Can't ya tell by the name) Distribution: na Organization: Sun Microsystems, Mountain View Lines: 33 From article , by emuleomo@paul.rutgers.edu (Emuleomo): > I heard that the average programmer produces 3-4 lines of *finished* > code a day! > This sounds ridiculously low. Does anybody out there know what the real > figure is? Or is it misleading to try and gauge productivity this way? > If it is, what are the recommended ways to measure programmer productivity > using some sort of metrics! I cannot tell you what the average is but I can say that as you measure the value grows. Human nature as it is says to maximize on that value that you are measured by. So if you want me to code 1000 lines of code a day I can (though it may be do nothing lines). But if you want me to develop a well structured robust code it will take longer AND BE FEWER LINES OF CODE. So how does measuring lines of code relate to programmer productivity? If I were measuring programmer productivity (of the top of my head so don't get to excited if I miss something obvious) I would set strict standards that deal with well written programs (e.g. IMHO a. few if any globals, b. one routine per file, c. well documented, etc.). Then I would use CodeCops or Graders or whatever you want to call them to see that the standards were followed and justify those times that they were not followed (there will ALWAYS be some). These CodeCops can then measure how well they can read the code, how many and the severity of the bug found in the code, how well the code stands up to user abuse, etc. Just the type of things that other engineers (mechanical, electrical etc.) are measured by. This method is more time consuming but it "MAY" measure that which you REALLY WANT to measure and not a programmers typing speed. This is one mans opinion.