Does it make sense to commit after every save with a DVCS?
- by blockhead
I know the question has been asked before how often to commit with a DVCS. All answers have one thing in common--as often as possible. But they're usually something like, after finishing a thought, a user story, getting code that compiles, or passing tests.
I was thinking, given that a DVCS gives you you're own repository, with very cheap commits, doesn't it make sense, to commit after every change to a file? After all, this is what happens in NetBeans, and you get a nice free "time machine" without even asking for it. If not every change, then at least every save, or compile.
Does this make sense, or do I have the wrong idea about DVCS. My feeling is that this not the workflow most people have with DVCS.
