Waiting (1 Viewer)

[Isaac]

I was a database developer at TSA. I got a lifetime of "letter names" jammed on me. Not being a cool aid drinker, I was very frustrating.

I'm a big proponent of, "stop using acronyms" in business settings. Half the people on the call might have no idea what it means and half the people using them are just trying to sound important by doing so at least about half the time.

Good communication in business settings demands people reduce their use of acronyms and just type or say it out all the way - this way you don't have people on the meeting that aren't understanding what you're saying.

Of course businesses need to have acronyms, but that doesn't mean people should verbally abbreviate everything all the time - a good communicator knows their audience and if in doubt, spell it out

 

[The_Doc_Man]

I don't mind acronyms because it becomes possible to have a translation table for JOIN queries to convert USMC to United States Marine Corps or USAF to United States Air Force. The ones that get me are the half-and-half abbreviations. The department where I worked was, at different times, COMNAVRESFOR Code 10 (Commander, Navy Reserve Force, sub-office #10), COMNAVRESFORCOM (Commander, Navy Reserve Force Command), and NAVRESINFOSYSOFF (Naval Reserve Information Systems Office). For that last one, we actually wanted to go full acronym but NRISO was already taken. Eventually, the Navy did yet ANOTHER realignment and we became NEDC NO (Navy Enterprise Data Center New Orleans), which was still easier than writing it out in full. I retired while that one was in effect so I have lost track of where they went.