Make sure your names are short and precise, but when in conflict favor precision. Strongly optimize around developer efficiency and make it easy to find files via “find by name” IDE shortcuts. Enforce good naming stringently with code reviews.
These four “clean code” tips will dramatically improve your engineering team’s productivity
Jonathan Fulton

I like that you’ve mentioned enforcing good naming conventions through code reviews. What other ways would you suggest for enforcing clean code practices?

Should basic linter rules be applied and required in all projects? Should all of these naming conventions and practices be clearly stated in a shared location for the whole developer team to see and use?