Lines of code doesn't really have much bearing these days, at least as far
as I'm concerned.

ie:

rc = generateInvoice(thePONumber);

is one line of code. But the lines of code behind generateInvoice() could
be thousands.

We also implement a lot of code that is open source, packaged, etc.

But I do work with shops where this may apply. :) RPGIII style code
copied and pasted from program to program to program. *shudder* Does
copying count as writing lines of code? :)

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #22 <https://www.bvstools.com/mailtool.html>: Low Total
Cost of Ownership!

On Wed, Aug 28, 2019 at 9:13 AM Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

I've searched the archives and haven't found anything on this subject.
Has anyone ever done a study or published anything on a standard number
of lines of code per day, for mid-range programmers?
Anyone ever evaluated this for hiring or retention purposes?

I know the old saw from the Mythical Man Month about ten lines of tested
code per day (for any language on any platform), but that can't be true
anymore, right?
So, I thought I'd start a firestorm here on the subject. Any thoughts?
--

Best Regards,

Thomas Garvey


--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.