Earlier quoted context omitted.
Here's the beginning of a metric: https://loup-vaillant.fr/articles/source-of-readability
Pretty good but regurgitated design patters overall, I'm not impressed. Moreover I personally find the part about "Don’t waste vertical space" too far gone, it would be better to switch to a more terse language like APL or derivative if wasted space is the impediment it's made out to be here.
I wrote "Nothing new of course." in the blog post itself, I am quite aware that it's a regurgitation of old stuff. Still, some of that old stuff is still being controversial, so I quite like giving it some theoretical backing.
> personally find the part about "Don’t waste vertical space" too far gone
Here's code I personally saw on the job, and it was mandatory, and the guy in charge of the silly rule that made it mandatory refused to change the rule, even though he admitted to my face the rule was silly:
/**
* Get the foo
*
* @return the foo
*/
int getFoo()
/**
* Set the foo
*
* @foo: the new foo
*/
void setFoo(int foo);
For something like 15 or more attributes, and this pattern was repeated across dozens of classes that I could see, and likely dozens that I didn't. Exactly like this, with comments that add zero information. And the rare times that it did, I kept missing it because it was drowned in a see of useless comments.Sometimes the code is too far gone.