Pretty much every such discussion demands linking:<p><a href="https://www.folklore.org/Negative_2000_Lines_Of_Code.html" rel="nofollow">https://www.folklore.org/Negative_2000_Lines_Of_Code.html</a><p>I would definitely agree that early on one writes more lines of code, while later development one spends more time finding where to make a change, and then reviewing the results of the alteration.<p>Curious how much attention folks pay to this sort of thing --- my current project: <a href="https://github.com/WillAdams/gcodepreview">https://github.com/WillAdams/gcodepreview</a> is a Literate Program and in its current state just crossed over 1,600 lines of code, but I'm re-working that so that each file will instead be numbered individually.
I once was asked to count loc using a tool another team developed, to measure code produced in the last 3 months.<p>They had imported about a year's worth of crap from a previous repository 2.5 months ago.<p>I noticed that the loc counter included all commented loc, so I made a legit file of several tens of thousands "loc", checked it in, ran the counter, made the report, was recognized for productivity, and thn reverted the comments.<p>Productivity, largely, is reducing loc while improving other quality attributes and features...
I use cloc[0], when I want to count my code (not often. It’s not a metric that really interests me).<p>It’s generally 50/50, between code (Swift, usually), and comments.<p>I don’t do the Java “one file for every class” thing, but I still like to keep my files relatively small, if I can.<p>[0] <a href="https://github.com/AlDanial/cloc">https://github.com/AlDanial/cloc</a>