3 ms·
my gut-feeling that 5 minutes of additional work while committing can easily amount to 30 minutes of effort saved later I don’t need to rationalize being anal
by sorbits 17y ago
my gut-feeling that 5 minutes of additional work while committing can easily amount to 30 minutes of effort saved later
I don’t need to rationalize being anal about my commits, of most I never visit again ;)
- dasil003 17y agoHowever when one causes a bug that you discover a few months later, being able to isolate the commit quickly could save you hours or days.
- pilif 17y agoYOU might not. But you might actually be nice to your coworkers (or open source project members) that do. It's just a matter of basic politeness to others. And in fact, I would reject a patch to any of my code out there that doesn't clearly separate different things into different patches. Too many times in my SVN days I witnessed strange bugs appearing in some commits that otherwise only contained whitespace changes labelled with the all-famous commit message "fixes". Never again.
- sorbits 17y agoNot sure why I was downvoted and get these replies. I wasn’t being sarcastic, I do spend lots of time making my commits (and everything else for that matter) ready for inspection by her royal queen — I know others with this same behavior, and my comment was merely meant to say “don’t rationalize it” — I do it to feel good, well, to not feel bad (about “leaving a mess”) is probably closer to the truth.
- bdr 17y agoI think people interpreted your comment as saying "You won't look at most commits ever again, so don't be so anal."
- apag 17y agoThat’s true, most of the time it doesn’t really matter. But it’s like properly formatting and indenting your source. Any one particular instance of sloppiness is irrelevant, but in the aggregate, the care you put into it really makes a difference in the feel of your works.