No, I’m talking about engineers and scientists communicating with project managers, designers, lawyers, business people, and the many many other people who work in the same industry but do not have technical backgrounds.
And I am talking about the fact that believing that nothing is complicated and that complexity is always made up can be a dangerous, anti-intellectual and anti-academic argument.
Of course, if you’re talking with people who don’t need to actually do the job and only understand enough of it, and you still speak like to a specialist, you’re not only in the middle, but also potentially (but not necessarily) kind of a dick.
But reading this and your example, and the fact we seem to be miscommunicating somewhat, I do wonder this: English is not my first language, what do you include in “technical science job”? Is it a specific job or group of jobs? I took it to mean any job with tech or science workers.
EDIT: further explanation of what went through in my head, which may clarify interpretation and intent. Having the management lingo example made me interpret that curve as a: all this jargon is just bullshit and you could do better without it. Definitely true imo with management lingo.
But what I was trying to say, maybe poorly, is that some technical jargon, in some areas, is meaningful. Explaining in layman’s term is dumbing down. Nothing wrong with that when it fits the purpose, but you still sacrifice something in the process.
I agree with everything you’re saying, but even speaking specialist to specialist, or say to a group of specialist colleagues who might not be working on exactly what you’re working on, you still often simplify away the technical parts that aren’t relevant to the specific conversation you’re having, and use specific language on the parts that are, because that inherently helps the listener to focus on the technical aspects you want them to focus on.
Anyone who took undergrad maths/science is not layman’s term.
I also disagree with this for the record but that’s besides the point.
It is for a white collar job where most people have degrees.
“amongst the people who understand the jargon and notations, jargon and notations are layman’s term”
Sure, I guess that’s true if you limit your sample, this is not what I took the meme to mean but ok.
No, I’m talking about engineers and scientists communicating with project managers, designers, lawyers, business people, and the many many other people who work in the same industry but do not have technical backgrounds.
And I am talking about the fact that believing that nothing is complicated and that complexity is always made up can be a dangerous, anti-intellectual and anti-academic argument.
Of course, if you’re talking with people who don’t need to actually do the job and only understand enough of it, and you still speak like to a specialist, you’re not only in the middle, but also potentially (but not necessarily) kind of a dick.
But reading this and your example, and the fact we seem to be miscommunicating somewhat, I do wonder this: English is not my first language, what do you include in “technical science job”? Is it a specific job or group of jobs? I took it to mean any job with tech or science workers.
EDIT: further explanation of what went through in my head, which may clarify interpretation and intent. Having the management lingo example made me interpret that curve as a: all this jargon is just bullshit and you could do better without it. Definitely true imo with management lingo.
But what I was trying to say, maybe poorly, is that some technical jargon, in some areas, is meaningful. Explaining in layman’s term is dumbing down. Nothing wrong with that when it fits the purpose, but you still sacrifice something in the process.
I agree with everything you’re saying, but even speaking specialist to specialist, or say to a group of specialist colleagues who might not be working on exactly what you’re working on, you still often simplify away the technical parts that aren’t relevant to the specific conversation you’re having, and use specific language on the parts that are, because that inherently helps the listener to focus on the technical aspects you want them to focus on.
Glad you agree that technical jargon can be used, and must be used, at the top of the bell curve. Be it always or sometimes.