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.
I've seen variations of this argument before on this list
(what background makes the best Tech Writer). All it
does is start a rather useless flame war. Let's not do
this again please.
pstaples -at- airwire -dot- com
> From: John Gilger <bjgilger -at- EMAIL -dot- MSN -dot- COM>
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: SACRED COWS
> Date: March 24, 1998 9:06 PM
> Hi Everybody!
> Since my last comments regarding writing samples stirred up so much
> let's shoot at another sacred cow.
> It is easier to teach an engineer to write than it is to teach a "writer"
> "technical communicator" to understand and explain engineering principles
> and technology.
> I have worked with both, as peers and subordinates, and the engineers are
> more productive every time. Of course, I write documentation for high
> 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.
> John Gilger
> "Those who can, do. Those who can't, teach. Those who can't teach stick
> around for a Ph. D."