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.
I have frequently had to create documentation "on faith" (based on designer
descriptions or the operation of some fairly sketchy prototypes knowing
that there may not be time to correct any errors). I'm sure everyone here
has had to do the same at least once. But I don't present the released
document as the result of significant soul searching or divine intervention.
Gene Kim-Eng
On Thu, Oct 25, 2012 at 12:00 PM, Lauren <lauren -at- writeco -dot- net> wrote:
> But that does raise issues of a writer's dilemma, where a writer needs to
> document the functionality of something that does not function or the
> rationality of ignorance.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Writer Tip: You have more time to author content with Doc-To-Help, because your project can be up and running in 3 steps.
See the “Getting Started with Doc-To-Help” blog post. http://bit.ly/doc-to-help-3-steps
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
