SJS wrote: > begin quoting Andrew Lentvorski as of Fri, Mar 28, 2008 at 06:01:14AM -0700: >> [EMAIL PROTECTED] wrote: >>> At an old job the resident programming guru was said to be amazingly >>> prolific. It was said he could work over a weekend and come back >>> with 6000 lines of code. > > Measured by wc -l? > > Easy. > > Measured by counting semicolons? Open/close braces? Method calls? > Assignment statements? > > Possible. >.. > And LOC is a lousy measure anyway, because cut-and-paste is a REALLY > easy way to get that number up there. (As is code generation -- CORBA, > RMI, lexers/parsers, etc., all can really inflate this sort of thing.) > > One of my most "productive" days ended up with ~15 lines of new code, > ~30 lines of modified code, and ~2000 lines of deleted code. (The > code I was fixing was the result of progressed being measured by the > number of new lines of code added by each programmer.) > > Ideally, we'd like to compare "completed features". >
Yes, a measurement(definition) of "productivity" is practically impossible. But, FWIW: http://www.dwheeler.com/sloccount/ http://en.wikipedia.org/wiki/Source_lines_of_code Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
