For 2020 I'm doing a 1 C++ Best Practice per retweet thread!

I wrote my first blog article about C++ best practices in 2007. In many ways I've been repeating myself over and over again for the last 13ish years.

And very little of what I say is novel.

Thread follows: Even though I've been repeating many of the same best practices for a while, I think my style is relatively unique.

One client told me "I like how you don't just give us a rule, you tell us why. <other guy> never gives us reasons."

There seems to be some confusion lately about what makes a great engineer and who you want to help you start up your organization.

There are really great engineers, and if you find one, you should try to keep them around.

They have these traits: 1. A great engineer sets up the project for success. They are concerned about tooling and reproducible builds. From the beginning of a project a great engineer has CI, static analysis, runtime analysis, source control, automated testing and anything else they can think of.