2 ms·
I once was asked to count loc using a tool another team developed, to measure code produced in the last 3 months. They had imported about a year's worth of cra
by readthenotes1 2y ago
I once was asked to count loc using a tool another team developed, to measure code produced in the last 3 months.
They had imported about a year's worth of crap from a previous repository 2.5 months ago.
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.
Productivity, largely, is reducing loc while improving other quality attributes and features...
- pressbuttons 2y agoNext step is to get recognized for simplification and "streamlining" of the codebase, by subsequent reduction.
- readthenotes1 2y agoIt can be taken too far, of course, but the amount of bad code and misleading comments in most systems is substantial. On a different company, two of our teams had a competition every Sprint to see who could take out the most code...
- pressbuttons 2y agoCompletely agree. It was a little tongue-in-cheek, but actually removing code and the complexity and tech debt associated with it is incredibly valuable. Especially if more experienced and knowledgeable engineers can remove the code paths that are "in use" but shouldn't be - premature optimizations that can be simplified, redundancies that can be eliminated, features that aren't bringing in value. It's usually an underappreciated job but can lead to greatly improved velocity and significantly less fragility.