> context, failed experiments, shortcuts, optimizations, and so on. I think commit messages are the appropriate place for this stuff; I use `git annotate` etc.

> context, failed experiments, shortcuts, optimizations, and so on. I think commit messages are the appropriate place for this stuff; I use `git annotate` etc. to find the information when I need it. I often have a 50-line commit message accompanying a one-line code change -- a ratio that would obviously make the code unreadable if all the comments were in-line with the code itself.