Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!usc!sdsu!csun!fedeva!premise!mirror!frog!john
From: john@frog.UUCP (John Woods)
Newsgroups: comp.lang.c
Subject: Re: 1000 lines of C a week?
Message-ID: <1548@frog.UUCP>
Date: 23 Jun 89 23:46:00 GMT
References: <18783@vax5.CIT.CORNELL.EDU> <7800012@gistdev>
Organization: Misanthropes-R-Us
Lines: 18

In article <7800012@gistdev>, flint@gistdev.UUCP writes:
> More seriously, I was asked to come forward with some lines-of-code produced
> numbers for the people on my staff....The results (over a year) ranged from
> 70,000 lines of code to 2,000 lines of code.  (My staff varies widely
> in their duties: some people are doing maintenance, where they spend 2 days
> trying to figure out what is causing a bug, and then add 1 line to fix it,

Uh oh.  I'm in trouble now.  I spent one hour yesterday debugging something
that I fixed by removing one line of code.  Let's see, over a year, that
works out to a productivity figure of, uh, -2000 lines of code.  I better
take up beekeeping instead...


-- 
John Woods, Charles River Data Systems, Framingham MA, (508) 626-1101
...!decvax!frog!john, john@frog.UUCP, ...!mit-eddie!jfw, jfw@eddie.mit.edu
    People...How you gonna FIGURE 'em?
    Don't bother, S.L.--Just stand back and enjoy the EVOLUTIONARY PROCESS...