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.
* "Rigorous analysis" includes "identifying the essential tasks to be performed and, most importantly, the interrelationships between the tasks."
* "Nobody" discusses "rigorous analysis."
* So, "incorrect documentation is pretty much gauranteed. [sic]"
Following the premises that you present can only lead to the conclusion that *all* technical documents are incorrect because "nobody" uses "rigorous analysis." Really?
You do not define "rigorous analysis," but apparently it is different than the analysis that the rest of us perform, although the requirements of analysis that you mention are a part of the analysis that the rest of us perform everyday. Somehow, in your head, failing to do things your way guarantees incorrect documentation. So you must have some great job security because you are the only one doing things right. I would really love to see your work. Does it possess the same quality as your posts?
Do you really think that you will win admirers by coming onto a technical writing forum and then insulting all technical writers for doing things wrong?
Lauren
-----------------------------------
Richard Lewis responds: It is easy to tell a TW to be correct, but, if that is as far as it goes, it is nothing. Being correct means having performed a rigorous analysis. Such analysis is based on identifying the essential tasks to be performed and, most importantly, the interrelationships between the tasks. Unfortunately, nobody within the TW community - either in academia or industry - has discussed this. So incorrect documentation is pretty much gauranteed. Generic Richard
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-