You kinda have to be specific if you want to avoid common names for things. Lets say I give you a menu and it says "Oven baked ground corn". If you ask me for it, do you expect to get cornbread or polenta?
Likely, the more popular option will be known as "Oven baked ground corn". The less popular, more contextual option would have an attached qualifier to distinguish it from the one most people want, such as "Oven baked ground corn porridge". That will of course lead to regional differences, but that's normal.
I'm asking to use "corn bread" and "corn porridge". You'll note that all of the words - "corn", "bread" and "porridge" - are common categories that can be combined with other common words to describe a great amount of meals.
What I'm asking is to stop the constant introduction of dish-specific unique terms (and renaming of existing dishes so that they sound more exciting), and instead use words that can be combined. That's the 101 of preventing combinatorial explosion. When you write code, your functions have arguments. You don't create zero-argument functions for every possible thing a program does and give them unique names.
