After reading Dune, I spent a little time thinking about the use of jargon in writing--where it's necessary, where it isn't, how to handle it, how it can be used for nefarious purposes, etc.
So, in case you don't know the definition, let's start with What is Jargon? Jargon is technical terminology or high-level language compared to the expected audience of the piece. So, if I talked about Bragg diffraction to a group of physicists, that wouldn't be jargon, but if I put it into a story, it would. This could also include the use of made-up or foreign-language words in fiction, for instance, a random Romanian word in a book not targeted at Romanian speakers.
Sometimes jargon is necessary. We need it when we need a precise description of a thing, such as the cobalt bombs of On the Beach or the psychohistory of Foundation. We also need it when we are introducing unique or novel constructs in our fictional worlds, such as Dune's stillsuits and Feist's Lesser and Greater Path magicians.
It's worth noting that novel jargon can be made more accessible by making compound words like stillsuit; the definition is in the word.
Sometimes jargon is unnecessary but helps to add flavor to the story. Proper names are a good example of this, such as Epasotl in Doomsday Recon. We may also want to show off cultural artifacts or phenomena which are part of the story, such as Clanspeak in Battletech, or unique month and holiday names in the Elder Scrolls setting.
It's worth remembering that whenever jargon appears for a good reason in the story, the author needs to make a good faith effort to explain the jargon either explicitly or through context. Sometimes flavor jargon only appears once, but even then it helps if there is some context to guide the reader's understanding. For example, the fictional month names in the Elder Scrolls world are mostly veiled references to what time of year it is, with references to harvest times, etc.
All of these uses of jargon are valid and can be great boons to your worldbuilding. However, some authors like to use jargon in ways that can confuse the reader or damage immersion.
One example is extensive use of large quantities of jargon which require the reader to spend a lot of time reading and trying to remember the meaning. In The Widow's Son, there were frequent sentences in foreign languages (mostly Spanish) that were often long enough that someone unfamiliar with Spanish would have trouble understanding what was said. Some of the context clues for the meanings of those sentences were too vague or too far away or even missing.
Using jargon when perfectly reasonable English terms already exist is another bad use of jargon. Perhaps one of the silliest and most egregious examples is illustrated here:
Another bad use of jargon is to create an illusion of depth, or to force a particular theme. One poignant example of this is the naming conventions in the anime Evangelion. Throwing darts at a bible in order to name things is neither depth, nor true attention to theme.
As a writer, here are some things you can do to ensure your jargon is reasonable:
Ask yourself...
- Is this jargon necessary?
- Is the reason behind it justified by the plot, characters, or setting?
- Is it organic and supported by context?
- How much am I asking the reader to memorize?
- Can I simplify it or make things easier to read somehow?
- Is the jargon slowing me down?
- Do thematic elements of the jargon actually fit?
- What jargon do I actually need to remember, and which can I let slide by?