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: Task-based versus UI-based documentation From:Gene Kim-Eng <techwr -at- genek -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 08 Aug 2014 19:04:24 -0700
There is no absolute answer to this question. As I've mentioned
previously, most of the software I've had experience documenting has
been in the area of instrumentation, and was highly customizable by
users. But on the hardware side, the launch control console for the
Trident II was solidly in the "Don't do ANYTHING we don't tell you how
to do" camp.
Gene Kim-Eng
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
