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.
replying from digest - forgive me if this thread has ended...
Tool knowledge is a nice-to-have, not a requirement. It should never
be a requirement. Knowledge and expertise in whatever it is the tool
aids in is the key. I'm pretty good with a hammer and saw, though I
would never call myself a carpenter nor would want anyone to hire me
to build a house for them.
Tools are tools, they are not the technology upon which anyone's
livelyhood stands. RoboHelp, HDK, Doc-to-Help, ForeHelp... they are
all tools allowing writers to work within a medium other than print.
What should the requirement be? Experience in WinHelp development, not
[place favorite HAT here]; experience in Web design, not [place
favorite HTML editor here]; and so on.
Anyone well-versed in the trade should be able to pick up a new tool
and use it proficiently within a reasonable amount of time.