Who’s in the room matters quite a bit.
When it’s only me and my team in the room, we use a lot of words that, to an outsider, don’t make much sense (at least not in context). We use words like Python, polymorphism, rubber ducky, spaghetti, API, DevOps, and git. That allows us to keep our discussion deep and nuanced but also highly efficient.
If, however, there are outsiders in the room, this technical terminology either shuts them out or leaves them behind. When we want to include others, we change the terminology and the explanations. The conversation may slow down and become less efficient, but it doesn’t have to lose its depth and nuance.
This is what good teachers and communicators do so well — bring others into the conversation without sacrificing the depth or nuance of the subject. They’re not dumbing it down; they’re attacking it from a different angle.
But technical terminology can also be used purposefully to shut others out or attempt to make oneself appear smarter. If you find yourself in a room and can’t understand the terminology, it might be that the talker is unaware or you aren’t the audience. Or it might be that the talker is using jargon to boost their status.
In any case, you should know who’s in the room.
