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: Educating Rita From:John Wilson <jwilson -at- AMADEUS -dot- NET> Date:Mon, 3 May 1999 10:46:00 +0100
I must disagree with Andrew who says that a technical writer's job is to
write documentation about what engineers design. User comprehension is the
end. Documentation is only the means, and only one of the means, along with
the design, user interface, and so on. If there is a hole in the road,
putting up a warning sign (documentation) is better than nothing, but it is
not the solution. The solution is to fix the hole. Similar reasoning is
applied to most professional activity.
