Jargon—friend or enemy?

Throughout the Dickens Fragment assignment I became aware of how much computer jargon is out there. Some of it is straightforward and understandable and some of the computer jargon I came across really sounds outlandish and it makes me wonder why would we even use it instead of standard English. Jargon does indeed serve its purpose. It eliminates the need for extensive explanation of processes and concepts (both simple and complex) within the conversational framework between peers.

But you can’t use jargon with someone who doesn’t understand it. Take knitting instructions, for example. If you are a non-knitter, then knitting instructions sound like mumbo-jumbo. The following is an introductory paragraph on how to complete a “long tail cast-on.”

“This cast-on is the favorite of many knitters. It creates a discreet edge that looks good with stockinette stitch and is stretchy enough to accommodate ribbing. It's easier to knit from than the simpler Backward Loop cast-on, and it's easy to execute once you get the hang of it. Recommended for beginners, or anyone.”

As information professionals we mostly likely will not be giving kitting instructions but we do need to be keenly aware of the words we choose when we are working with someone to meet his information need. Shop talk may feel comfortable for those in the field but it is confusing and frustrating for those who don’t understand it.