re: Form habits by making the right thing easiest VIEW POST

TOP OF THREAD FULL DISCUSSION
re: I just found this answer and also support Jesse Philips way. I feel your argument of being lead developer and setting good examples, but one good e...

I do think that committing too frequently can be a problem. Vim is my version control before I make a stamp, but it only does one file.

What is the downside of commiting too frequently in your opinion?

When a change is "trivially small" (a rarity), leaving just a commit title without additional detail works just as well of course. Adding the extra detail on somewhat larger commits helps me understand what I just did by recapping, and may also help another developer spelunking in the commit history someday. In terms of productivity I don't find myself spending a great deal of time on it...it's just jotting notes :)

Too mutch shuffling between different attempts could lead to difficulty in navigation the different attempts.

I reference vim because, like emacs, it has undo trees. Vim has a decent concept of an edit. If I extrapolate vims edits to commits I would find the history to be invaluable.

code of conduct - report abuse