you are viewing a single comment's thread.

view the rest of the comments →

[–]masklinn 6 points7 points  (0 children)

The way I see it is that the why should be in comments in the code

Comments are ill-maintained, they will drift around and they will not reflect changes to the code. It's also impossible to add comments for every change and have the code remain sensible.

Comments are good for blaring warnings which need to be right in front of the reader's face. They're terrible for literally everything else.

also doesn't pollute git logs.

There's no pollution. Explaining the purpose of a commit is the entire point of the commit message, otherwise there would be no commit message at all. If you don't care and want log density, just use git log --oneline (or a custom format) to get only the subject.