Re: Lines of code per day?

Many years ago the contracting company I worked for took over a major development that was badly behind schedule.

Turned out that all the file definitions (and there were many, many files) were manually copied into each source file to up the line count because the payment schedule was based on "progress" and "progress" was defined in terms of lines of code. The result of course was chaos during development as every time a layout changed they had to change every copy of it (and frequently missed bits). We switched to using COPY to bring in the definitions and most of the programs shrunk by about 40%. Became much more manageable after that.

I cured me of ever thinking that LOC was a good measure of anything!

On Oct 3, 2019, at 5:32 PM, Musselman, Paul <pmusselman@xxxxxxxxxxxxxxxx> wrote:

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