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: Best Documentation From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:kay -dot- robart -at- integratedconcepts -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:Wed, 09 Feb 2000 09:09:07 PST
Tony Markatos responds to Kay Roberts (see below):
SME's can create very good technical communications. I usually work as a
Systems Analyst. When I do TW-type work, it is to:
* Create especially difficult documentation. For example clear, concise
software requirements specs for complex software systems.
* Fix-up botched end-user documentation. I'm am not going to say who, on
more than one occasion, botched-up these jobs; I would be 'flammed' from
hear to eternity!
Tony Markatos
(tonymar -at- hotmail -dot- com)
Kay Roberts said:
....we [Technical Writers] frequently do not consider subject matter
experts like programmers and engineers capable of writing good
documentation........many do not have the writing skills to write
comprehensibly to the reader. They are not taught to express themselves for
any audience other than other subject matter experts, they cannot adapt the
vocabulary if that is needed....[continues on with 900 other reasons why
SMEs can not write].
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
