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: since/that, because/which From:Iain Harrison <iharrison -at- SCT -dot- CO -dot- UK> Date:Wed, 2 Oct 1996 13:36:02 GMT
Sanford writes:
>>
PLEASE!
TECHNICAL writing. Not grammar, not software, not ...
<<
... but neglects to:
1. define what TECHNICAL means to him
2. understand that technical writing usually involves writing about technical
subjects
Here there are umpteen technical people, many of whom are more
qualified and knowledgeable than I. They don't write the manuals
because they can't write.
Being able to bounce ideas off colleagues at the next desk or on the
other side of the world can help to clarify a way to clearly and
succinctly describe a complex process.
It can be the grammar, style and syntax of the documentation that
gives an impression of competence and quality to a product. It
matters!
3. realise that the tools of the trade are important to technical
writers.
If I have spent hours and days getting some recalcitrant software to
work properly, because what we do pushes it to its limits, I am glad
to be able to share that experience with others. Similarly, I
appreciate the help and advice of others who have covered ground that
is new to me.
If you want technical-only discussion, perhaps a writers' list is the
wrong place to look?
