Just simply state what you mean. Let the other person ask questions if they need clarification.
Just simply state what you mean. Let the other person ask questions if they need clarification.
For example, "I would like one head of lettuce" is a kind of jargon-lite for "I would like one portion of the fully-grown plant known as lettuce which is found above-ground as a connected unit in nature." Which one leads to a "simpler" exchange will depend on your assumptions about the recipient.
Most of this business-speak jargon is incomprehensible to people who haven't heard it before in the workplace. It seems "normal" to people like us here on HN because most of us have interacted with these sorts of business types (or are even one of them), but I would guess that most of the people who know what a head of lettuce represents would have no idea what ROI or noun-form "solve" means.
Just that "simple" is deceptive, non-universal, and sometimes contradictory.
For example you can use P2P to explain how some gossip spread or you can say that your relationship with SO is like UDP recently.
Jargons are shortcuts to pre-agreed ideas. Just a tool.
Certainly someone who gets it will, well, get it. But in general it seems like a lot of effort in most cases to gauge whether or not the recipient will understand at the level you hope. Even the UDP example could be misunderstood by someone who is well-versed. Unreliable? A good low-level thing to build stuff on top of? These are both plausible meanings, but would convey very different things.
Better to just use clear language.
Once I had a physicist friend freak out over my use of "exponential" to loosely explain something because he instantly began thinking about edge cases and obviously using "logarithmic" would have been more precise. We were not on the same page with the jargon, but then again I guess it requires social skills too so that you can pick where the analogy starts and ends.
"Hmm udp, so ...unreliable and...hmm...but high throughput?...hm, good to build stuff on top of?"
I have no idea what that is supposed to mean, yet I know exactly what udp is.
If you just meant "unreliable", how was this better than just saying that?
Also, you use it in context. The jargon becomes illustrative for the analogy, not precise definition. After all, human can't have UDP connection.
It's not. Well, if the person you're talking to happens to get the intended meaning immediately, it's a cute in-joke. To me, that's the only real (dubious) benefit.