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: When it is right to be wrong? From:"Lisa Wright" <liwright -at- earthlink -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 6 Feb 2002 22:47:30 -0800
Thanks for raising this point. It did get lost in the thread where it
I'd like to put in a vote for being straightforward with the user about
a) shortcomings in the documentation ("we don't yet have this
information"), b) shortcomings in the software ("be careful here: it's
easy to make a mistake" or "this feature is not yet programmed"). I'd
like a doc set in which all the important information is addressed at
least in this manner. I'm hard pressed think inaccurate information is
worth the time it took to write it.
This is NOT about the speed with which information can be made obsolete
by changing circumstances. But, for the record, when I have worked in
production environments, the documentation is always up-to-date unless
the developers are slamming new code directly into production (bad
programmer, bad!), AND the users get release notes/notification of
People will respect and appreciate honesty and real information.
On Behalf Of John Cornellier
Sent: Wednesday, February 06, 2002 8:01 AM
A little while ago [Darren Barefoot, I think] wrote:
"Get it done, then get it right, then get it pretty. ... I'd rather have
a complete documentation set that's 90% accurate than an incomplete doc
set that's 100% accurate."
I agree about the pretty part. But I can't think of any situation where
inaccurate documentation is better than no documentation.
Did you know you can get RoboHelp certified?
To learn how, visit http://www.ehelp.com/techwr. Be sure to also check out
our special pricing offers and promotions for RoboHelp 2002.
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.