Comment Re:Documentation is a tech skill (Score 4, Informative) 81
While I understand that sometimes it's a communication skill, or a habit thing, I wonder if sometimes the lack of an explanation is itself a red flag that whoever opened the PR or made the commit lacks understanding of what they were supposed to do, and what they actually did...
On the other hand, ticking off a checkbox item so that the linter passes by putting in useless information is the same as a garbage test written to make sure there's sufficient code coverage to make a linter pass. A waste of time and further muddying the waters by forcing someone to read through both the code, the documentation, and the test, to determine that there's no additional value to the documentation or the test over the code.
I guess this would be the point in time to discuss how aggressive to be in terms of adopting forced syntax reformatting, pre-commit and commit linters, and tests? And god forbid, checklists for each commit?