We want to live our domain. We want to eat it, to consume it. Most of all, we want to share this language from user to code.
This is the ubiquitous language.
It is free from ambiguity. We talk about these things. In our codebase, we find classes and objects named after these things. The ubiquitous language, the language we all use, eliminates impedance... it puts us all on the same key... it is all how we get along
You are a developer. It is your responsibility to create the ubiquitous language.
Hard, you say it is? Impossible, you claim?
Excuses!
"Try not. Do or do not. There is no try." Master Yoda is right...
It is your responsibility, as a developer, to make the language consistent, to make the language ubiquitous.
You might think of yourself as an "Human Compiler." I'd say 90% of the time you're wrong... unless you're making drivers or OSes (all inhuman things), you're most likely making applications that normal, everyday people use.
If you're an application-type person, you're probably modeling some kind of business. Don't think of yourself as a Ruby or Java or C# or Haskell programmer... think of yourself as a business model maker!
##Sorry But It's Basic
If there's ambiguity in the business language, that's a stop-drop-and-roll moment. Sort it out and get on the same page. I know this sounds like Yogi Berra / overly-simplistic advice, but it's true. Get on the same page, it is up to you.