I'd bet that establishing good documentation habits could go a long way here. Just writing down some project guidelines/constraints. Loose rules for the type of ways you name things? If you have a theme of how things are generally named than the right consistency might come to you.
One more thing: Good tests and regular refactoring. If you do happen to get in a situation where you'd like to make areas of the code more consistent, being confident that you can make sweeping changes without breaking things is a good place to be.
I'd bet that establishing good documentation habits could go a long way here. Just writing down some project guidelines/constraints. Loose rules for the type of ways you name things? If you have a theme of how things are generally named than the right consistency might come to you.
One more thing: Good tests and regular refactoring. If you do happen to get in a situation where you'd like to make areas of the code more consistent, being confident that you can make sweeping changes without breaking things is a good place to be.
Great advice. I especially like the suggestion for creating rules for naming things. Thanks!