3 ms·
While commit messages are always there, they get lost. You fix a bug in your code, with a commit message. Later, you realize that this function is super reusabl
by elygre 7y ago
While commit messages are always there, they get lost. You fix a bug in your code, with a commit message. Later, you realize that this function is super reusable, so you move the function to another class in another file. Now, for all intents and purposes, the original commit message will never be seen again.
- jacques_chester 7y agoIt's harder to find originals under such circumstances, sure. But I don't see this as a reason for never writing good messages, because a journal of intent is strictly better than a journal of physical amendments. That something needs to be entirely perfect before being judged better than the status quo is the Nirvana fallacy.
- RussianCow 7y agoI don't think anyone is arguing for "never writing good messages"; the point is that you can have both good commit messages and good comments, both of which are useful for different reasons, and you don't need to give up one to have the other.
- elygre 7y agoThe parent thread was very much about using commit messages instead of comments, and I was arguing against that. Two rights, on the other hand, don’t make a wrong.