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.
> If someone
> had ASSUMED I was an expert with a software application and did not take
> the time to spell out the acronyms I would have been lost. DO NOT
> ASSUME!!!!
I'd agree with this in most cases, but not the one that started this
thread. I think this is a perfect example of when you *should* assume.
It was a job ad that called for someone with RDBMS experience. If (like
me) you don't even know what RDBMS stands for, you probably don't have
the experience the employer wants and are not qualified for the job, and
there is really no need to spell it out. In fact, since it acts as
pre-screening device, it would be counterproductive to spell it out.
