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: Interesting Article... fewest jobs lost in Tech Writing
Subject:RE: Interesting Article... fewest jobs lost in Tech Writing From:"Jane Carnall" <jane -dot- carnall -at- digitalbridges -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 8 May 2002 17:33:08 +0100
Dan Hall wrote:
>I use Word pretty much every day, and I've never read any
>Word documentation. But if Word wasn't coded, or didn't have
>a GUI, I'd be in tough shape.
I see your fine distinction, and such as it is <g> I take your point. OTOH,
I have been using Word professionally (on and off) for my entire career as a
technical writer, and I *have* read the Word documentation. (The online
help, that is. I used to help my dad *with* the Word documentation back when
they used to produce a cr -at- ppy manual.) I have also read a bunch of stuff
that ought to be in the official Word documentation if Bill Gates had
one-billionth as much common sense as he has US dollars - like the website
with the Seven Laws of outline numbering that I cited earlier today.
You can use Word, badly, without ever reading the documentation: it has a
sufficiently good user interface for that purpose. You can, with sufficient
experience (=hard knocks) learn to use Word well without ever reading the
documentation.
With a sufficiently good user interface, you can figure out a lot of things
with a GUI product without reading the documentation, and increasingly GUI
might as well stand for Good User Interface.
However, I write documentation for a product with a GUI: and it isn't a bad
GUI at all, as these things go. But the things that you can do with this
product are sufficiently complex, and it matters enough to my company that
they are done well, that no GUI is good enough to school the users through
the Kindergarten of Hard Knocks. Is the documentation part of the product? I
haven't asked if that's how they think of it. Will they willingly ship a
version of the product without the documentation? Nope. For all practical
intents and purposes, the documentation is part of the product.
Jane Carnall
The writers all stand around a cauldron chanting and occasionally tossing in
a small manual. Unless stated otherwise, these opinions are mine, and mine
alone. Apologies for the long additional sig: it is added automatically and
outwith my control.
E-mail is an informal method of communication and may be subject to data corruption, interception and unauthorised amendment for which Digital Bridges Ltd will accept no liability. Therefore, it will normally be inappropriate to rely on information contained on e-mail without obtaining written confirmation.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
Buy RoboHelp Office in May and you'll save $100 with our mail-in rebate.
Or switch from Doc-to-Help or ForeHelp to RoboHelp Office for only $499.
Get the help authoring tool PC magazine recently awarded a perfect score!
Go to http://www.ehelp.com/techwr
---
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.