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: Decomposing From:"Steven J. Owens" <puff -at- netcom -dot- com> To:BEllison -at- UTS -dot- Itron -dot- com Date:Fri, 10 Dec 1999 10:32:36 -0800 (PST)
Beth Ellison writes:
> Whether it's correct or not, it just sounds bad. Or at least,
> funny. If I read it in a professional document it would distract me
> and make me doubt it. And distractions and doubts are best left to
> programmers:) You gotta love a thesaurus.
This comment highlights the critical question that everybody
seems to be oblivious to, which is, *who* is going to be reading the
document in question. Decomposition is in fact a jargon term used in
certain neighborhoods of the programming world. It has a specific
meaning and is understood in specific contexts. If the match between
those contexts and the intended audience of the document is good, and
the term is being used properly, then it is appropriate.
Sheesh. No wonder programmers and engineers start to get
obnoxious opinions of technical writers. This reminds me of the
inane, long-winded discussion back in '93 or '94 about the
"male-oriented terminology" inherent in "Retry, execute, abort?".
(And if you want to know why *that* is inane, send me private email).