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.
A debate about whether the documentation is wrong or the
system is wrong seems pointless. Obviously, the product is
wrong. The maker of the product should:
change the system to match the documentation,
OR change the documentation to match the system,
OR change both to match some 3rd standard.
The fact that we usually see the documentation as wrong is
just a by-product of the fact that changing the document is
usually the cheapest fix.
Jim Shaeffer (jims -at- spsi -dot- com)
> -----Original Message-----
> From: Tom Murrell [mailto:trmurrell -at- yahoo -dot- com]
>
> I realize this all sounds familiar to anyone who has worked
> in a software environment; it's really a common situation.
> What was a new expeience for me was sitting in a conference
> call with a German engineer who was insisting that the
> system wasn't functioning properly BECAUSE the documentation
> said the opposite of what the newly release system was doing.
>
>
> I tried and I tried, to the point of yelling, to convince my
> colleague that the > documentation was wrong, not the system,
> but he continued to insist that since my document said A,
> it must be write. "It is in the manual," he kept repeating.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Experience RoboHelp X3! This new RoboHelp release combines single sourcing,
print-quality documentation, conditional text and much more, into the most
monumental release of RoboHelp ever! http://www.ehelp.com/techwr-l
Enhance, optimize and automate your FrameMaker-to-PDF workflow with TimeSavers:
Define all PDF features in your source FrameMaker files ONCE, distill MANY.
Bookmark Controller, Link Controller, UnBloat & more : http://www.microtype.com
---
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.