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.
Re: Paul's message. I agree that it shouldn't take a writer 3
years to learn how to write online documents -- that seemed off-
the-wall to me. But apart from that, the estimates presented
seem reasonable. I think these estimates are for genuine online
documents, not page-based documents distributed electronically
(aka electronic documents). I think they are estimates for ideal
circumstances, and should be taken as such.
I disagree that the time is all spent on the learning curve for
the tool. There's a lot of structuring required in creating
online documents, and it is different than the kind of structuring
we're accustomed to in books. To produce a *good*, usable online
document, the author has to spend quite a bit of time planning its
structure, which can be especially difficult if the online document is
being derived from paper.
I also agree that there is often a gulf between academic theory and
reality, but in this case I don't think it's as big as Paul is
suggesting. Also, this gulf can serve a useful purpose. While I
almost never have time to do my work the best possible way or spend
as much time as I think is needed on a given project, the theorists
provide something to aim for by discussing what can be done under
ideal conditions. If I had to do every project as I do now, and didn't
have any hope that I might be able to improve on that, work would
become both boring and depressing in short order!