4 ms·

I disagree that the vast majority of commit messages are you describe. But even if that were the case, I don't think the majority of commit messages being bad w

I disagree that the vast majority of commit messages are you describe. But even if that were the case, I don't think the majority of commit messages being bad would mean they don't matter.

falcolas 4y ago
Thought exercise: If comments are often considered harmful because of their lacking quality, why would commit messages be considered helpful when they suffer from similar issues?
- marcosdumay 4y ago
  One reason is that commit messages do not become stale. Anyway, software development as a whole decided on a pretty stable set of comments that are considered helpful. Commit messages are clearly in there, as well as API elements description.
  - staticassertion 4y ago
    > software development as a whole decided on a pretty stable set of comments that are considered helpful. I have no idea what you're talking about.
- usrusr 4y ago
  In addition to the staleness argument (which is somewhat countered by its inverse: the good, helpful commit message might be hidden under a huge layer of naming convention changes and the like), there's also the off by default. A comment always helps itself to some mental bandwidth, whereas the commit is nicely tidied away unless you ask for it.
mmcdermott 4y ago
Descriptively, I do find the default level of rigor to commit messages to be low. Even in repos with really good messages, it is an act of discipline to get them that way and keep them that way. And if there is anything we should all be able to agree on, it's that strong discipline is not the norm in software development as a whole. Note I'm not arguing for that as a prescriptive state. I think a good commit log is a good thing and can see that there are different ways of getting there.
staticassertion 4y ago
> I disagree that the vast majority of commit messages are you describe. Sorry but I feel like you have to be just in denial then. > But even if that were the case, I don't think the majority of commit messages being bad would mean they don't matter. OK but I think if it's the case it's fair to say hte majority of developers don't agree, whereas you stated it was an industry wide opinion that they are. I think commit messages are mostly stupid and the git UX is absolute trush. Theoretically, if the git UX weren't trash, they could matter, but it is so they don't.
- michaelmior 4y ago
  > you stated it was an industry wide opinion I never claimed to be stating an industry-widr opinion. I was disagreeing based on my own personal experience. Based on upvotes and other comments, it seems I am not alone in this opinion.

I disagree that the vast majority of commit messages are you describe. But even if that were the case, I don't think the majority of commit messages being bad would mean they don't matter.

falcolas 4y ago

Thought exercise: If comments are often considered harmful because of their lacking quality, why would commit messages be considered helpful when they suffer from similar issues?

marcosdumay 4y ago
One reason is that commit messages do not become stale. Anyway, software development as a whole decided on a pretty stable set of comments that are considered helpful. Commit messages are clearly in there, as well as API elements description.
- staticassertion 4y ago
  > software development as a whole decided on a pretty stable set of comments that are considered helpful. I have no idea what you're talking about.
usrusr 4y ago
In addition to the staleness argument (which is somewhat countered by its inverse: the good, helpful commit message might be hidden under a huge layer of naming convention changes and the like), there's also the off by default. A comment always helps itself to some mental bandwidth, whereas the commit is nicely tidied away unless you ask for it.

mmcdermott 4y ago

Descriptively, I do find the default level of rigor to commit messages to be low. Even in repos with really good messages, it is an act of discipline to get them that way and keep them that way. And if there is anything we should all be able to agree on, it's that strong discipline is not the norm in software development as a whole. Note I'm not arguing for that as a prescriptive state. I think a good commit log is a good thing and can see that there are different ways of getting there.

staticassertion 4y ago

> I disagree that the vast majority of commit messages are you describe. Sorry but I feel like you have to be just in denial then. > But even if that were the case, I don't think the majority of commit messages being bad would mean they don't matter. OK but I think if it's the case it's fair to say hte majority of developers don't agree, whereas you stated it was an industry wide opinion that they are. I think commit messages are mostly stupid and the git UX is absolute trush. Theoretically, if the git UX weren't trash, they could matter, but it is so they don't.

michaelmior 4y ago
> you stated it was an industry wide opinion I never claimed to be stating an industry-widr opinion. I was disagreeing based on my own personal experience. Based on upvotes and other comments, it seems I am not alone in this opinion.