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.
You know, I have a fairly flip response to tools requirements. If I'm asked
about my tool expertise (I don't have it on my resume), I sort of laugh a
little and pooh-pooh the idea. I'll say something like, "Oh, I don't worry
too much about what tools I use. I have preferences, sure, but I can use
what you have." I explain that I've been using computers for about
eleventy-bajillion years now, and I make a living writing documents. DTPs
and graphics tools pretty much all work the same (within subsets). Different
tools have the features in different places. That's OK. I'll find them.
At least in my field, I guess I wonder how it is that someone could expect
me to fumble my way through a complex, half-implemented telecommunications
provisioning tool or something well enough to write a user guide about it,
yet be completely baffled by something like Microsoft Word. It just doesn't
make sense to me.
