I often find code I've written that uses different vocabulary for the same things. For example, we have a term
variant (referring to a variant of our product), but sometimes it's written as
variation. It's an absent-minded, honest mistake, but once it's in and used in different interacting codebases, it's really hard to get rid of.
Another common source of confusion is using the same word to mean different things. If I sat down I bet I could find at least three completely different usages of the term
build (just from the top of my head, it could mean: a configuration, a build artifact, a ci job, a particular run of a ci job - hey, that's four already!).
So my question is: how do I improve this? I'd like to be mindful of my word choices because I feel like it has a huge impact on the readability and maintainability of the code (not only positively: when it's less than ideal, those metrics suffer, too). At the same time, working on 6-7 interacting codebases, it feels impossible to keep all the wording the same. Any advice?