Comment Re:Documentation (Score 1) 23
That's why I personally despise a lot of the "clean code" nonsense. Oh, "no comments, your code must be self-explanatory" my ass. You just cannot explain complex concepts in a subroutine or variable name. Comment your code, with good sense. In extreme cases, if it's too long or needs images, you can very well include other documents along with the code in a "doc" folder. But never let yourself or others alone with just code.
And Git commit messages are documentation too. And a pretty good one. When you're doing a "blame", it's just wonderful when the "what, who and why"s are right there in the commit message, no need to scramble around looking for information. I just hate when I stumble in a lasy ass "fix: bug fix" message (no shit Sherlock), specially when the perpetrator is not available anymore.