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.
> It is easier to teach an engineer to write than it is to teach a "writer" or
> "technical communicator" to understand and explain engineering principles
> and technology.
> If you want to be a good, well-paid, tech writer, get a BSEE or BSCS then
> get the hell away from those ivory towers.
That's quite a generalization. Many of us do NOT spend our days
documenting what engineers and programmers do and would find an EE or CS
degree pretty well useless. Not all technical writers document software
or hardware, so could we please get out of that box?