AWS is probably the worst in this regard...so many services with names that give no indication about what the service actually does.
Meaning the long and awkward "descriptive" name becomes a lie over time. But the "code" name has no meaning, so it doesn't become wrong, you just need to maybe re-learn the meaning of the otherwise meaningless word.
See also: How do you descriptively describe the replacement/rewrite that does the exact same thing, but exists in some form while the other one does, also?
How often is it that you have a service that drastically differs in purpose from it's original intent? Can you give an example of how that comes about?
And usually not too long after I've coined a fun name for a project, I wind up feeling like it's cringy, and start to loathe when other people talk about it.