Agreed. The author claims to write a "substance" guide rather than a "style" guide, but many of these points boil down to style over substance.
(Edit: This is not to say that there can't be multiple good stylistic options, just more that the bad ones by far outnumber the good ones and at the end of the day it does matter how your code looks if you plan on supporting it for a long time)