Using lines of code to measure effort and developer productivity often feels like something that would be another good example for this article.

For example, 20 lines of code in Java might easily require 200 lines of code in assembly language. In addition, measuring lines of code says absolutely nothing about code quality.

Sometimes you come across serious, and glaringly obvious, examples of how the wrong code could kill SEO for a website. And believe it or not, that sometimes could be just one line of code.

While fewer lines of code are not always better (at some point it leads to obfuscation), they usually are, simply because there's fewer things to keep track of when trying to understand the code.

History has shown that lines of code, number of bugs fixed, etc. are an example of Goodhart’s Law — “when a measure becomes a target, it ceases to be a good measure” — in action. When companies have ...

Most artificial intelligence systems can be advanced by adding more: more computing power, more lines of code, more analysis, more neural networks, more machine learning. With only five lines of ...

Last weekend, some anonymous “specialist” told the New York Times that “5 million lines of software code may need to be rewritten” in order to fix the mess that is healthcare.gov. (The ...