This is the right answer. And I’ll go one step further: Discuss it, dictate it, then automate it. (Sorry, couldn’t find another alliterative word.) My point being: whenever possible roll these best practices into build tools (auto formatters, style checkers, static analysis, etc) and then fail builds if they violate these standards. That way it’s impossible for engineers to get them wrong.

There are definitely things that can’t _yet_ be automated like this but do as much as you can.

We still encourage discourse on our standards if engineers have opinions about them but you’ll never get widespread adoption without some sort of enforcement.