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: Word up From:Emru Townsend <etownsen -at- Softimage -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 1 Dec 2000 09:37:44 -0500
> > The fact is, Word is just a tool. If you can't produce docs
> in Word, the
> > problem is likely you and not Word. Just because the tool
> does not conform to
> > your vision of a perfect universal order, does not mean
> that tool is inherently
> > flawed and should be taken off the market.
> >
>
> Mostly, I agree with you. Part of being a professional is knowing
> how to make do with the tools you have.
Bruce hints here at the third, possibly most common scenario in our field,
which Andrew seems to forget.
How about when you know it's not the best tool for the job, but you there
are inherent limitations in the software... and your boss doesn't want you
to use another tool? I'm reminded of my first two TW jobs where I made
reasonably detailed arguments as to why certain tools/methods weren't the
best choice because _the tools themselves_ didn't allow for us to do what we
wanted. I was overruled anyway.
Much as I agree with much of Andrew's sentiment (though not the snide tone),
I have to take issue with his bipolar view of the universe, where writers
are either good (they can do anything using even a pencil and barely-dry
flattened pulp), or evil (can't write worth a damn and hide their
worthlessness in processes and tool knowledge either real or imagined).
"If you can't produce docs in Word, the problem is likely you and not Word"
is a canard. Anyone who reads in this forum knows that a common problem we
have is management -- with little or no knowledge of what we do -- making
our tool decisions _and_ setting our objectives for us. Yes, a moderately
talented individual can make docs sing using only Word, but I think it can
be generally agreed that Word is not a tool made with technical writers in
mind. As such, there will be times when even the most expert of writers
will not be able to create the docs as required using the tools given.
Regardless of his level of expertise, if you hand a carpenter a screwdriver
to drive a five-inch nail into a block of wood, he can't do his job
properly. Andrew, is it so hard to concede this point?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Take XML and Tech Writing courses online! Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off! http://www.online-learning.com/index.html.
---
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.
