Hacker News new | ask | show | jobs
by ali_m 1883 days ago
I think the goal is to provide practical guidance to developers. Splitting it into N different lists seems strictly worse in this regard.
1 comments

> Splitting it into N different lists seems strictly worse in this regard.

Not at all. If I could find three lists:

- common imprecise language used by developers, and how to improve it.

- common grammar errors among developers.

- San Fransisco deep-left political preferences wrt to code documentation.

I would know which two which would be of use to me, and which one I should absolutely ignore.

Well, it's a policy document for Google developers, who presumably aren't free to just pick and choose which rules to follow.

I personally agree with ~95% of the list, and the other 5% seems too trivial to be worth arguing over. I couldn't care less about the motivation behind the rules (political or otherwise) as long as they don't sacrifice clarity, and I think that's basically true for everything in here.