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.
GM> Judging by the advertisements for technical writers - contractors and
GM> permanents - the principal skill sought is technical expertise or
GM> knowledge (often of some programming language or operating system).
GM> Writing skills appear to take the back seat. In view of the fact that it
GM> can take a moderately intelligent person weeks to master a new system,
Sorry, you lost me here. This statement shows an equivalent ignorance
of the people with whom you deal and their domain(s) of expertise.
No flame: I'm guessing you're a little frustrated.
GM> but years to master clarity and precision in writing, this ranking of
GM> skills seems, on the face of it, a trifle perverse. What do technical
GM> writers think about this? If you were the client (not the 'server'),
GM> would you prefer a technical whizz who could also write well, or a
Given that the whiz makes most of the product I'm buying, well...
GM> good writer who was also cluey in the technical realm? (Don't cheat and
GM> say both: you are asked, here, to RANK the two skills: writing expertise
GM> versus technical expertise.)