
I remember when I first went to work at NASA I felt as if everyone around me was speaking in a foreign language. This was because just about everything from space shuttle to space station components and launch operations were referred to by an acronym. This would be particularly annoying to non-NASA spouses at company parties, who had no clue what those around them were talking about if they started talking shop.
Your reader might have the same problem if you use too much terminology that is unfamiliar. While you want your story environment to sound authentic, this is an area where you may want to consider including a glossary, though these are awkward to access in ebooks, as are footnotes.
When I was a technical writer, the rule (at least at NASA) was to write it out the first usage in that particular document, then include the acronym in parenthesis. From that point on the acronym would be used. In a book this might work, depending on how often it will be used as well as how soon after you define it. If it’s something that isn’t obvious from the context of the sentence or conversation, you might need to ditch the acronyms and go with something the average reader immediate understands.




When you do, by all means celebrate! You deserve it! But don’t think for more than one glorious day that you’re finished. No matter how great your work seemed as you put it down on paper initially, chances are it can be improved. Probably a lot, depending on whether this is your first book or tenth or more.



