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: And the Correct Answer Is...... From:Christine Lienhart <clienhart -at- PREVUENET -dot- COM> Date:Thu, 12 Feb 1998 07:55:30 -0600
Michael Maloney wrote:
>As for the advice forwarded by well meaning technical writers
regarding
>Christine Lienhart's question, most, if not all recommendations
were wrong.
>(I'm glad she didn't ask how to fix a broken leg.)
Michael,
I appreciate your enthusiasm for asking qualified people for
advice (and "advice" is what I was in search of, not a right or wrong
answer), however, technical illustration is indeed a part of technical
writing, and I'd venture to say that most of us out here have some
experience with it. It's that experience I was hoping to draw on when I
posed the question. The fact that there are also folks here who
specialize in technical illustration is just gravy for me!
>The actual answer to Christine's question is "none of the
above". Despite
>her comprehensive description, without "seeing (or at least
interviewing)
>the patient" no proper analysis, diagnosis or solution should
be offered.
Well, then, if that is the case, none of us should offer our
opinions on any subject out here, since we NEVER get the opportunity to
"see the patient." I believe that the unwritten disclaimer here is that
the opinions expressed are based solely on the personal experience of
the writer AND the information supplied them by whoever posts the
question. The person asking the question can glean whatever solution
they like from the responses he or she gets. I did this when I reviewed
the responses I got and found a solution most suitable for my document,
my budget, and my timeframe.