I'm not sure how your and others feel about it, but I'm more on the lines of "less comments, better commit messages" (see [every line of code is always documented](http://mislav.uniqpath.com/2014/02/hidden-documentation/))

Basically, someone that wants to understand why that `_is_test()` exists can `git blame` me and read the reasoning at https://github.com/ckan/ckan/commit/cc7e91743d179964dcf271875bc10db64b6fc0c9.

That's why my commit messages sometimes get a bit big, and I often repeat the pull request description into it (so we don't depend on GitHub).

I agree that it's more work for the reader, but with good tool support (like [fugitive.vim](https://github.com/tpope/vim-fugitive)), it's easy.

I usually only comment on very hairy parts of the code, when I couldn't make it easy to understand. For others, I prefer on relying on `git blame` (which is why I think good commit messages are very important).

What do you think?