There's also the fact that it discourages negative amounts of LOC per day, which often results in bugs not being fixed because that's an operation where there's a high likelihood of a net loss of lines of code.
The only moments where I use LOC as a metric is when doing initial scoping for a source code review, and even then, it's barely useful.
/y
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Musselman, Paul
Sent: 03 October 2019 22:32
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Lines of code per day?
Doesn't equating 'lines of code' to productivity encourage sloppy programming and excessively large programs, just to up the lines of code??
We used to have a programmer who was enamored with a huge Xerox printer. But the only way to justify the printer was to print X thousand pages a month. So he created large reports and distributed them to people who didn't need or want them, just to keep the printer busy.
Same idea.
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
