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.
> A "good technical writer" can't do those things?
Depends on the time allowed and the complexity of the
things they need to pick up.
A "good tech writer" who has never touched a developer
product might fail if thrown into a live API project,
especially if expected to not only fully document the
API but supply completely integrated context-sensitive
help for it.
I don't think anyone's saying a person can't learn or
adapt. I think the heart of the message is that demand
is IMMEDIATE and in many cases learning time is seen
as not an option.
=====
Goober Writer
(because life is too short to be inept)
"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
-- Geoff Hart
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
