"clarity relates to your expertise, the less expert phrasing is sometimes overly verbose and destructive to quick comprehension, while the expert phrasing may seem incomprehensible to the non-expert. "
An expert programmer should write adequate code for the target audience - the people who will actually read and work with that code later. They need to understand it, so he or she should not use advanced constructs, when beginners will work with the codebase.
Likewise with scientific language:
If you speak to fellow scientists you can and must use your special language. Way more efficient.
But if you give a press conference to present your findings, you have to use simpler terms, if you want people to understand you.
Many great discoveries probably got lost that way, because scientific language was not translated adequately.
many professions have concepts that are complicated to understand for people outside the profession and as such develop their own jargon.
The development of jargon that is perceived as unfriendly and complicated to people outside the profession is often driven by the need for greater clarity inside the profession.
Finally in the case of programming languages and clarity arguments, clarity relates to your expertise, the less expert phrasing is sometimes overly verbose and destructive to quick comprehension, while the expert phrasing may seem incomprehensible to the non-expert.