RE: One more thought on "Fast" and "Slow" Writers

["Jocelyn Olivier" <jolivier -at- calendra -dot- com>]

You should know that sometimes software writers have to "see and foresee things" too: In small software companies, the technical writer must start producing documentation long before a beta version is generated. Specs and SOR are not always available and some features assessed by the TW for the manuals sometimes serve as development orientations.

Did you know that 40% software products not released on time are due to unavailable documentation?



-----Original Message-----
From: letoured -at- together -dot- net [mailto:letoured -at- together -dot- net]


You and the other software writers don't get it.  Its not having more time --
its not taking more time because its available -- it has nothing to do with
personality or style. 

Its taking more time because its **necessary**  It has nothing to do with
diminishing returns.  People writing in areas beyond software have to think
about and address -- they have to see and foresee things -- that software
writers never even have to think about about. 

That is what takes more time.  That is why you go slow and carefully.  



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l

  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit http://www.raycomm.com/techwhirl/ for more resources and info.