Years ago a read a piece in which it was postulated that when aliens come to pick through our ruins they'll have a difficult time with language because of acronyms.
That problem has probably multiplied exponentially with the advent of computers, and even more-so with texting!
When I worked at Texas Instruments we had a published manual of acronyms that as I recall was well over 300 pages in length. The same acronym might be used in multiple divisions and/or disciplines but with a totally different and unrelated meaning in each it might be used in multiple contexts within the same major project again with totally different or even worse somewhat similar meanings. There also might be multiple acronyms for the same identical "thing".
As a Software Design Engineer working in a training branch I once fought with a PhD educator for several months to convince him the documented Software Requirements Analysis process was procedurally identical to the Training Needs Assessment process he was writing. The only significant difference being one process description used software engineering jargon and the other used education jargon. (He was finally convinced but never forgave me because I had reduced his planned two year project to less than two weeks worth of copy and paste.)
I am convinced some level of mis-understanding is inevitable in any inter-disciplinary discussion and the deeper you get into the disciplines the more frequent and greater the level of mis-communication.
zlf? = IF typed in a hurry and hitting SUBMIT before a thorough proofreading. 🤦🏻♂️