4 ms·

For the developer working on the change, or for the reviewer + everyone that comes after them looking at your commit (which can include your future self)? We t

by pavas 5y ago

For the developer working on the change, or for the reviewer + everyone that comes after them looking at your commit (which can include your future self)? We tend to discount everyone else's time but our own. Might also be worth thinking about long term asymptotic effort vs marginal effort at a particular point in time--typically, the more often you do something (decomposing a commit into multiple independent parts, in this instance), the easier and less time-consuming it becomes.

pengaru 5y ago
> For the developer working on the change, or for the reviewer + everyone that comes after them looking at your commit (which can include your future self)? Both. I don't really follow what you're getting at, I think we're in agreement? confused
- pavas 5y ago
  Yes we are; I thought you were advocating for larger commits since they're too difficult to break apart into logically independent pieces, but it seems I just misunderstood what you wrote the first time I read it.