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

OK, so that was a good example of how noindex and nofollow could hurt a blog or website SEO-wise. Now let’s take a look at an example of how one line of code could kill SEO for an ecommerce website.

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.

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 ...

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.

Google share stats on the volume of code it manages and, not surprisingly, it’s a whole heck of a lot.