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.
Since my last comments regarding writing samples stirred up so much comment,
let's shoot at another sacred cow.
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
I have worked with both, as peers and subordinates, and the engineers are
more productive every time. Of course, I write documentation for high tech
engineering projects, so the view is admittedly biased.
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.
Fire off that email, this ought to be an interesting discussion.
"Those who can, do. Those who can't, teach. Those who can't teach stick
around for a Ph. D."