Interesting (reverse) approach to developing and committing:
“What if instead we start by writing our commit message, a succinct note of what we want our next chuck of development to accomplish and we work on that until the commit message captures what we have in our code.”
Many times I struggle to recall exactly what was done when it comes time to commit something. If I make the change relatively fast, it’s easy, but the longer I take (and the more things I find to fix), the longer the list in my head grows (and the more likely I’ll leave some important information out in my commit message).
Although – the other stuff has to be done anyway, so committing more is not necessarily a bad thing. You just want to be sure your commit messages relate to exactly what was changed. It will make things much easier in the long-run when debugging.