Yah. If your big project has 2 kinds of objects, handles, designators, whatever that are used frequently... and their alternative english names are awkward, long, and/or misleading... give them a short pronounceable name. I endorse this 100%.
Don't do it 15 times, though, because then it's going to slow down onboarding more than the benefit you get.
Comments
I feel like that complaint is somewhat addressed by the blog post itself:
It sounds like your company culture has gone crazy with it, which, yea, I would think it would make it hard to reason about.
I think this kind of naming approach could be...reasonable in a shared code base, if used very sparingly and well documented.
Yah. If your big project has 2 kinds of objects, handles, designators, whatever that are used frequently... and their alternative english names are awkward, long, and/or misleading... give them a short pronounceable name. I endorse this 100%.
Don't do it 15 times, though, because then it's going to slow down onboarding more than the benefit you get.