TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: FIFO From:Len Olszewski <saslpo -at- UNX -dot- SAS -dot- COM> Date:Tue, 4 May 1993 09:15:42 -0500
> I don't know...
> Isn't this introducing yet another acronym/jargon term into your documents?
[...deletions...]
> So what purpose will FIFO serve? How will it enhance a reader's
> understanding of arrays? And how can we use it in the least confusing
> way possible?
> Anatole Wilson
> Masters in Professional Writing program, Carnegie Mellon University
Well, playing the devil's advocate:
1 - Rather than new jargon, FIFO is old accepted jargon. I'd
rather stick with current jargon than create new stuff.
2 - As a metaphor with an established, clear meaning, it helps
those familiar with the original term visualize the array
processing that mimics it.
3 - Saying FIFO is shorter than saying "first-in-first-out" in a
manual describing array processing.
You'd have to balance the potential confusion against these advantages,
assuming you agree they *are* advantages.
|Len Olszewski, Technical Writer |"Don't use the imperative!" |
|saslpo -at- unx -dot- sas -dot- com|Cary, NC, USA| -Rhetorical contradiction |
|---------------------------------------------------------------------|
| Opinions this ludicrous are mine. Reasonable opinions will cost you.|
