In my efforts as a software engineer, when creating new systems, I consistently explore metaphors to gain a better understanding of what I'm attempting to achieve. And then I transpose those metaphors onto my virtual system by using terms related to that metaphor in my code. Literally, this means naming variables, classes and functions things like "Path", "Node", "Walk", "Disease" and "Create". Choosing the wrong words has time and again thrown me off in the wrong direction.
I could chose such abstract symbols as A, B and C rather than any terms with implicit meaning. But this would prevent me from quickly exploring and attaining a new understanding of what I am doing through the powerful tool of metaphors. Choosing the right metaphors and terms can result in an unexpected creative explosion.
When it comes to how we comprehend the world, I could use terms like "mind" and "memory" and "physical reality". But if I did, I would be potentially trapped in the classical interpretation of such words. Sometimes I I find it more useful to shift, if not entirely replace such terms in order to better grasp the world through new and improved metaphors. Sometimes, of course, an old perhaps quasi obsolete word is the key to understanding our lifeworld.
What is for certain from my perspective is that words and symbols make a difference. If I were to use PSI instead of EPSILON for an negligible float point I would initially confuse myself on encountering my code at some future time. I would have to recalibrate, relearn my own terminology.
So, summa summarum: words matter.