Google Developers Don’t Write Their Comments
betterprogramming.pub
betterprogramming.pub
This is wrong in most cases. Documentation should change as the app changes. In some documentation systems its possible to version the docs nicely, and keep them inline with the application version, but for lots of documentation that we write that's not the case. It's important to go back and edit documentation to add, remove and update sections as the world around the application changes. Documentation that fails to reflect the reality the user is working in is incredibly frustrating.
EDIT: To be fair to the author, they actually say as much in the post, but the format of a "call and response" they've chosen doesn't make their intent very clear at all (slightly ironic considering the topic). If you're going to write in a way that refutes the 'parody' points don't put an image in between the point and the refutation.
As it is I came into it expecting that at Google during a review process (perhaps?) comments are written in the code by reviewers.