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 18:24:01 -0400
> -----Original Message-----
> From: Lauren [mailto:lauren -at- writeco -dot- net]
> Sent: Tuesday, May 06, 2008 5:28 PM
> To: 'Bonnie Granat'; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Definition of Tech Writer, was STC is broken
>
> > From: Bonnie Granat
>
> > You are using a non-standard definition of technical writing.
> > I am viewing
> > technical writing as the term that encompasses all specialized
> > writing--business writing, for me, is therefore a subset of
> technical
> > writing.
>
> Evolution is non-standard in that rules change over time. A
> strict definition that does not include the evolution of
> business writing should receive discussion. Perhaps not here, though.
>
I'm not speaking in any sense except the main categories of types of
writing. I think the changes within the subsets of technical writing aren't
relevant at this point.
If you agree that software documentation is different from manufacturing
process documentation, and that both are technical writing, then you are
basically agreeing that technical writing is the umbrella term for various
types of writing. You'd just have to view business writing as having the
same degree of specialized knowledge and view science writing, and legal
writing, in the same way. What makes something technical is that it involves
"skill" ("techno").
> An allegory could be the evolution of man. If we define man
> in the strict terms of Neanderthal man, then a discussion of
> man in civilization would follow a non-standard definition.
>
I'm sure you meant "analogy." However, there is late-breaking news on the
Neanderthal front you might want to check out.
> However, I would not hold any premise that business writing
> evolved from technical writing. I would, however, hold that
> technical writing evolved from written communication and
> non-technical writing evolved from written communication.
> Both forms of writing borrow from each other and each form of
> writing is distinct from the other.
>
> People here do not agree and seem to hold a technical writing
> supremacy ideology. Whatever.
>
You're certainly free to reject the most widely held definition of technical
writing if you like.
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-
