I've been sat in seminars in my group (on computer science or engineering topics) and had the same feelings as the author. People invent jargon to describe simple ideas and then convince themselves that it's more precise when it rarely is or, when it is precise, the precision isn't necessary. All it ends up doing is reducing the impact of the research. But it does help with the imposter syndrome of being an early-career academic – everyone else is using all this complicated jargon and you feel a bit like a fraud, so you need to get to grips with it quickly.
This isn't a problem unique to academia though it might be more severe there. There's a section on the gov.uk's 'Writing for GOV.UK' [1] article that I like:
"Government experts often say that because they’re writing technical or complex content for a specialist audience, they don’t need to use plain English. This is wrong.
Research [2] shows that higher literacy people prefer plain English because it allows them to understand the information as quickly as possible.
For example, research [3] into use of specialist legal language in legal documents found:
- 80% of people preferred sentences written in clear English - and the more complex the issue, the greater that preference (eg, 97% preferred ‘among other things’ over the Latin ‘inter alia’)
- the more educated the person and the more specialist their knowledge, the greater their preference for plain English"
[1]: https://www.gov.uk/guidance/content-design/writing-for-gov-u...
[2]: https://gds.blog.gov.uk/2014/02/17/guest-post-clarity-is-kin...
[3]: http://works.bepress.com/cgi/viewcontent.cgi?article=1000&co...