Another way of looking at it is that "finding the right word" often means find the good "fit" between abstract concepts shapes or feelings, and a construct of known language items. That's precisely what you're doing as a developer.
But it is an assumption indeed... Only it is based on my personnal experience.
As for the comment mentionning google developpers, the ones i see are good enough verbally to talk about their jobs at google i/o.
See https://news.ycombinator.com/item?id=5911235
Mathematicians perform very well on programming contests, but they are usually terrible software engineers.
Anyways, I was just kidding :)
The former (e.g. a data scientist) will be good solving a problem but bad building a big architecture. The latter, the other way around.
I guess the question is which kind of programmer you are and which skills to look for.