Percentages are misleading. How many lines in a diff are actually relevant code? Anyone who does reviews knows the answer. That is one of the reasons why lean

Percentages are misleading. How many lines in a diff are actually relevant code? Anyone who does reviews knows the answer. That is one of the reasons why lean, terse languages are often better to review. We can guess by those companies preferred coding styles and technologies whether their codebases are lean and terse or full of straw. And that should give us an estimate. Of course, I could be wrong. They could be doing this measurement after removing irrelevant changes. The better choice would be not to publish those sorts of claims if there is not a clear methodology that explains how the number was achieved.