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.
Re: Writer vs Author (was Techwriting after the boom)
Subject:Re: Writer vs Author (was Techwriting after the boom) From:"Bonnie Granat" <bgranat -at- editors-writers -dot- info> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 8 Jun 2003 05:23:32 -0400
----- Original Message -----
From: "Mark L. Levinson" <mark_levinson -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: June 08, 2003 05:05 AM
Subject: Re: Writer vs Author (was Techwriting after the boom)
>
> Bonnie writes:
> > Technical writers are not technical authors.
>
> I thought that technical authors were the same
> as technical writers but in England.
>
> What's supposed to be the difference between
> a technical writer and a technical author?
> Are you considering that a technical writer
> is more like an editor? (And if so, where
> does that leave the technical editor?)
>
>
All of the technical occupational descriptions provided by government, by
private industry, and by the educational establishment state *primarily* that
technical writers *explain* technology or scientific concepts to a lay
audience. There is no occupational designation for technical author. I believe
that that term is now used to distinguish between technical writers and SMEs
who write books and articles. That leaves technical editors (like me, when I
wear that hat) in the clear. ;)
I consider a technical writer to be a writer who has training in rhetoric,
critical thinking, and communications. In addition, the technical writer has
an *interest* in technology of all kinds and a joy in learning about
technology and science. Common sense tells me that a technical writer who
hasn't a clue how a chip is made is not going to prance down to Intel and
expect to be hired to write manufacturing procedures. Common sense tells me
that a technical writer with no understanding of relational databases is going
to apply for a job documenting databases.
As I've said before, in other posts, there are no doubt certain technical
writing jobs that require a depth of understanding that is quite high. And
yes, the more you know, the better. But technical expertise is simply not a
requirement. The ability to write coherently *is* -- and as I've said, I find
bad thinking and bad writing to be the primary cause of bad documentation.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.