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.
Subject:RE: Definition of Tech Writer, was STC is broken From:"Bonnie Granat" <bgranat -at- granatedit -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 6 May 2008 00:22:04 -0400
Technical writing is about far more than "style." It has to do primarily, in
fact, with content. Any kind of writing has its particular style; technical
writing is so named not due to the style of writing but to what is written.
Business writing is a subset of technical writing.
A person who writes for business 100% of the time (not "some of their
writing") is a technical writer. That's the classical view. I don't know
that an alternative view that holds that business writers are not technical
writers has caught on anywhere.
-----Original Message-----
From: techwr-l-bounces+bgranat=granatedit -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+bgranat=granatedit -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Lauren
Sent: Monday, May 05, 2008 5:53 PM
To: 'Gene Kim-Eng'; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Definition of Tech Writer, was STC is broken
> From: Gene Kim-Eng
> Peoples' sense of identity regarding their work is inseparably tied to
> what they do and what they are called. Tell writers who identify as
> technical writers and write about banking procedures that what they do
> is not technical writing, and you have told them that they are not
> technical writers and are not entitled to their identities, including
> the job titles that they have worked to qualify for. Imagine for a
> moment that I proposed a definition for the role of technical writer
> that excluded what you do, whether you think it's technical writing or
> not. Did you really think you could do that to someone else without
> starting a controversy?
I never stated nor suggested that technical writers were not technical
writers because some of their writing is business writing. I never got into
the discussion about the validity of a person's job title. My discussion
has always been focused on the fact that business writing is not synonymous
with technical writing. There are different classes of writing and one
writer can write in each class.
A technical writer can produce some business documentation without giving up
the title of technical writer. Anyone who writes a procedures manual is
performing technical writing because procedure manuals fall under the class
of technical writing. If that person also prepares a financial summary,
which is business writing and not technical writing, then that person has
not relinquished the title of technical writer, but has incorporated a style
of writing that is not technical writing.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
