|
On Aug 28, 2019, at 2:43 PM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:
Does the apparent disregard for LOC metrics mean that no one is developing applications/systems from the ground up anymore?
Seems like responses are all about support type environments.
No one has reviewed a recently completed new application to see how much each LOC actually cost?
Best Regards,
Thomas Garvey
On 8/28/2019 1:06 PM, Rich Loeber wrote:
The other day, all I did was move a single line of code down in the program by three lines. It took me several hours to track the problem down. That doesn't count as much in the way of lines of code, but it resolved an open problem for a dozen customers.--
Rich Loeber
Kisco Information Systems
http://www.kisco.com
------------------------------------------------------------------------
On 8/28/2019 12:47 PM, Jon Paris wrote:
Or in pointing out to the requesting user that they are idiots and their proposed "solution" won't help! <grin>
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Aug 28, 2019, at 12:09 PM, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
On Wed, Aug 28, 2019 at 11:05 AM John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
The *fundamental* problem with thinking about LOC is that it is basedIMO, a programmers 'job' is to solve problems.
on the premise that the job of a programmer is to write code.
Usually we solve problems by writing code ... but sometimes we solve
problems by identifying problems in procedures, user education, or
finding finding 3rd party solutions.
david
--
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding in the American Diabetes Association's Tour de Cure to
raise money for diabetes research, education, advocacy, and awareness.
You can make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.
You can see where my donations come from by visiting my interactive
donation map ... https://mideml.diabetessucks.net/map (it's a geeky
thing).
I may have diabetes, but diabetes doesn't have me!
--
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
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 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.
midrange.com
