Abstraction isn't to gatekeep; it's to increase the utility. It's the same as "dependency inversion" in programming: do your logic in terms of interfaces/properties, not in terms of a particular instance. This makes reasoning reusable. It also often makes things clearer by cutting out distracting details that aren't related to the core idea.
People are aware that you need context to motivate abstractions. That's why we start with numbers and fractions and not ideals and localizations.
Jargon in any field is to communicate quickly with precision. Again the point is not to gatekeep. It's that e.g. doctors spend a lot of time talking to other doctors about complex medical topics, and need a high bandwidth way to discuss things that may require a lot of nuance. The gatekeeping is not about knowing the words; it's knowing all of the information that the words are condensing.
People are aware that you need context to motivate abstractions. That's why we start with numbers and fractions and not ideals and localizations.
Jargon in any field is to communicate quickly with precision. Again the point is not to gatekeep. It's that e.g. doctors spend a lot of time talking to other doctors about complex medical topics, and need a high bandwidth way to discuss things that may require a lot of nuance. The gatekeeping is not about knowing the words; it's knowing all of the information that the words are condensing.