When, if ever, is “number of lines of code” a useful metric? [closed]
I’d say it’s when you’re removing code to make the project run better. Saying you removed “X number of lines” is impressive. And far more helpful than you added lines of code.
I’d say it’s when you’re removing code to make the project run better. Saying you removed “X number of lines” is impressive. And far more helpful than you added lines of code.
StatsD operates over UDP, which removes the risk of carbon-aggregator.py being slow to respond and introducing latency in your application. In other words, loose coupling. StatsD supports sampling of inbound metrics, which is useful when you don’t want your aggregator to take 100% of all data points to compute descriptive statistics. For high-volume code sections, … Read more
On my latest project I used SourceMonitor. It’s a nice free tool for code metrics analysis. Here is an excerpt from SourceMonitor official site: Collects metrics in a fast, single pass through source files. Measures metrics for source code written in C++, C, C#, VB.NET, Java, Delphi, Visual Basic (VB6) or HTML. Includes method and … Read more
On one of my current projects, in some modules, I am proud to have contributed a negative line count to the code base. Identifying which areas of code have grown unnecessary complexity and can be simplified with a cleaner and clearer design is a useful skill. Of course some problems are inherently complex and required … Read more