I take the alternate approach to this, which is to let the compiler warnings (and other related tooling, like static analyzers) drive how I write the details of

I take the alternate approach to this, which is to let the compiler warnings (and other related tooling, like static analyzers) drive how I write the details of my code. I think it leads to a higher average code quality than the micromanagement approach where the details need to be perfect. In particular, as soon as you have multiple contributors, people tend to have inconsistencies in how they prefer doing things. Having some tooling enforcing all this really helps in killing unproductive arguments :)