RE: Structure vs. Substance?
Sorry, I'm going to have to disagree with you here. Most documentation================================================
flaws I've encountered were directly due to lack of the necessary
On the "bad" projects where I've either worked or been called in to fix,
the writers were often woefully uninformed about the product.
Being "woefully uninformed" is a whole lot different from lack of necessary
information. Which is it? Was the information not there, or was it
there but the writers didn't know how to acquire and interpret it?
they were uninterested in playing with the product, becoming users,
trying to set it up and make it work as intended, or anything you might
assume they'd need to do. Instead, they were more interested in having
information spoon-fed to them by functional specs, developers, and other
So what do you do if the product being documented is the Stealth
Bomber or an Air Defense System? Start a war and put
the writers in the plane or the air defense bunker?
You have a very narrow view of the tech writing profession if
you think it consists only of writing user manuals for software GUIs.
| Nullius in Verba |
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory -at- primenet -dot- com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
majordomo -at- omsys -dot- com with "subscribe framers" (no quotes) in the body.
Search our Technical Writing Archives & Magazine