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'd offer that an important challenge presented by this article to this
group is to imagine some other software, not something that controls
machines, but something that is used by humans--that is, a situation where a
"user manual" is required. Certainly there are such instances where safety
and reliability are just as important. How about aircraft maintenance? So
then, any ideas on incorporating the tech writer and the manual writing
process into systems with similar safety/reliability requirements as the
space shuttle systems? Could a similar work culture exist in the different
circumstance? Would it work?
