|
|
|
|
|
by majormajor
2204 days ago
|
|
You're starting to contradict yourself a bit, I think. Will I disagree that good test suites or well factored code or systems docs are more important than commit messages? No. However... most projects do not have those things and most developers on those projects are in a "I don't know what I'm missing" sorta state where they don't bother adding them. Exactly like you point out for good commit messages. So if 95% of projects have inconsistent and incomplete test suites, never-refactored spaghetti code, and almost no system docs, that doesn't mean we should tell people not to try to do those things. In the same way that the existence of poor commit messages doesn't mean we shouldn't try harder. The nice thing about commit messages, being a small and simple thing, is that it would be much easier for someone to learn how to write good commit messages overnight than to learn how to write a good test suite, or to refactor their code. |
|
If you've reached the point when the next "optimization" you can do is to work on your commit messages, that is awesome.