Nowadays developers, and others, have the habit to use Git or other version control systems when writing software. While the benefits of this are mostly seen by means of pull/merge requests, easy "undo" functionality, team collaboration and others, the real benefit is history. When did we change this piece of code, and more importantly: why?

By using clever commit message and branch strategies, you can reconstruct the way your or your colleagues' brain was thinking a year ago! It will help you pinpoint the exact ticket where a client requested a specific change and by who it was sanctioned.

Start keeping a diary today, and write history!

Comments

Comments are closed.

This talk contained a bunch of good info on how handle commits and write good commit message given by an enthusiastic speaker. I very much appreciated the live examples on the command line.

My only suggestion: start with the live examples sooner in the talk.