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.
Bruce Byfield added an important note to my previous post:
<However, I also suspect that, sooner or later, most writers are going
to find themselves faced with learning something they know nothing
about.
I suggest that, when this situation arises, the best model for a
tech-writer is that of an investigative reporter: somebody who knows
how to find information and make sense of it quickly.>
I know I'm not learning enough in one or two courses to be a true
business area expert. But I do learn enough to help me do a better job
of investigating. When I have a tight deadline (no time to do outside
learning) I definitely take the investigative reporter approach.
My suggestions referred to the "extra" things that have helped me write
requirements. I hope I didn't imply that they are a replacement for any
of the other things we need to do as technical communicators. They
aren't.
