Complaining about jargon is lazy. Most communications about complicated things are not aimed at the layman, because to do anything useful with the complicated t

Complaining about jargon is lazy. Most communications about complicated things are not aimed at the layman, because to do anything useful with the complicated things, you tend to have to understand a fair amount of the context of the field. Once you're committed to actually learning about the field, the jargon is the easiest part: they're just words or phrases that mean something very specific. To put it another way: Jargon is the source code of the sciences. To an outsider, looking in on software development, they see the somewhat impenetrable wall of parentheses and semicolons and go "Ah, that's why programming is hard: you have to understand code". And I hope everyone here can understand that that's an uninformed thing to say. Syntax is the easy part of programming, it was made specifically to make expressing the rigorous problem solving easier. Jargon is the same way: it exists to make expressing very specific things that only people in this subfield actually think about easier, instead of having to vaguely gesture at the concept, or completely redefine it every time anybody wants to communicate within the field.