Rule #1: write commit comments before coding
Rule #2: write what the software should be supposed to do, not what you did
Please, help me to understand what I’m missing.
I’m in love with git, and I’ve been devoting a lot of time and efforts in promoting it in the companies where I used to work.
I always found hard to effectively communicate to TFS, svn and cvs users the paradigm shift that git requires. Depicting information and ideas turned out to be the most successful approach.
Yet, visualizing information is an art.