Hi Thomas:

You wrote:

“..I do agree with him if we narrow this to buzzy business speak. By contracts, legitimate technical jargon serves a purpose, allowing experienced specialists to communicate more quickly in order to solve problems. ”

Out of curiosity, can you offer some examples of legitimate technical jargon that you think accelerates problem solving? I agree that there it does exist, but most of what passes at technical jargon obscures more than it helps. As a recent example from my own experience, calling something a “metadata infrastructure”, when “database” will do, has more to do with ego and inflation than speed and problem solving.