And, 9/10 times between mutually aggrieved parties there is no shared definition of aggression.
So, no, it's not that easy.
And, 9/10 times between mutually aggrieved parties there is no shared definition of aggression.
So, no, it's not that easy.
To paraphrase Fred Brooks: "Show me your arguments and conceal your definitions, and I shall continue to be mystified. Show me your definitions, and I usually won't need your arguments; they'll be obvious." (s/flowcharts/arguments/ and s/tables/definitions/ from the original.)
Insisting that everyone in the room uses the same definitions for all words, and trying to force some mono-mind of language, rather than actually working to solve problems is counterproductive. It can be productive to discuss and understand how terms are being used differently by different parties, and it is absolutely necessary for everyone in the room to understand that words are different for different people, but then you have to actually start working on the shared problems.
It's incredibly frustrating when people waste everyone's time trying to come up with a completely new shared "compromise vocabulary" that no one is happy with and will get discarded the moment people leave the room.
As a non-political example, the first time I heard the term "server-side rendering", I thought it was one of the soonest ideas I had ever heard. With the latency between client and server, needing to go back to the server for every screen draw would make for an incredibly laggy interface. I hadn't known that JavaScript developers use "rendering" to refer to making HTML, whereas I associate it only with making an image to be displayed. Because there was no shared definition, communication was harmed.