Five reasons to write proper commit messages

We have all been there and probably done it ourselves. An app randomly breaks or crashes, so you type “git log” to see what has changed recently. And BOOM! The history reads like: 18:15: More updates. 18:02: Updates. 17:40: Updates. 16:34: Fixed. 12:22: Done. 08:23: Complete. And usually it’s not even punctuated correctly… I can…