tl;dr:Six years ago, David Thompson wrote a popular blog post called “My favourite Git commit” celebrating a detailed commit message. I enjoyed the post at the time and have sent it to several teammates as a model for good commit messages. I recently revisited Thompson’s article as I was creating my own guide to writing commit messages. When pressed to explain what made Thompson’s post such an effective example, I was surprised to find that I couldn’t. I couldn’t justify it as a model of good software engineering.
tl;dr:Michael quit his job at Google to go solo three years ago, focussing on his own projects. This is his annual report of what he's learned - (1) Product/market fit is magic. (2) You can build a successful business without being available 24/7. (3) Success is more stressful than failure.
tl;dr:Many tips, including review your own code first, write a clear changelist description to provide context, conduct your review after your code passes all automated tests, and more.
tl;dr:Michael left Google two years ago and has lost money both years, intentionally. He discusses how he's designing his life so he can focus on optimizing for side projects that can become businesses.