Comment by koolba
10 hours ago
> A good goal as a developer is a high commit message to change ratio. The more lines of code that you change, the more comments explaining why you’re changing the code. More message and less code changes per commit is generally a good idea.
No! Blanket statements like this is how you end up with 40 pages of slop AI comments in PRs that nobody reads.
Comments should be terse and meaningful. They should document surprising behavior or choices. The less comments you have, the more meaningful each one becomes because your time and eyeballs are limited as well.
We shouldn't tolerate slop in any form, especially not in commit comments. What we should care about is communicating design decisions, intent, and especially we should explain concerns that can't be intuited from reading the code. A longer, more detailed comment that explains some significant detail can be especially valuable but it should earn the weight that it carries.
I think we're all in agreement that a one word "runs" commit and a 6 paragraph slop commit both fail to communicate effectively.