I personally read and write a lot. I track things in git messages by cross-referencing issues, and I comment my code.
But my point is: when you have a cultural divide among competent programmers on whether to comment, not commenting game-theoretically wins, because the outcome where you have comments that get updated some percent of the time is worse than not having those comments.
Instead, embed what you want to say in a comment in the code itself, or in a test.
Documents your libraries and APIs if they are used by people outside your team.
But my point is: when you have a cultural divide among competent programmers on whether to comment, not commenting game-theoretically wins, because the outcome where you have comments that get updated some percent of the time is worse than not having those comments.
Instead, embed what you want to say in a comment in the code itself, or in a test.
Documents your libraries and APIs if they are used by people outside your team.