RE: Style guides - doc standards vs processes

["Steve Hudson" <steve -at- wright -dot- com -dot- au>]

Again - the flipside. So, what IS it you do for your job then Andrew? You
just try and repeat your results each time without ever defining the process
and resources required? When a client asks "How long will this take?" you
reply "It doesn't really matter, I will do it for you"?

I cant say it often enough, we need to be able to deliver consistant results
in variable environments and the only way to do this is to rigourously and
regularly review and define one's working practices. Otherwise there is no
progression from a target you only dimly understand.

Steve Hudson , HDK List MVP
Wright Technologies Pty Ltd (Aus)





-----Original Message-----
From: Andrew Plato

Is there any time left for doing your job? While all of these things are
nice to have written down, this is secondary, one-off work. This type of
stuff should be developed in down-times.

And yes, you should be able to write documentation without a formal style
guide and documentation plan. The best style guides emerge naturally out
of writers doing the documentation and making decisions about the material
as it is being written.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Be a published author!  iUniverse gives you: a high-quality paperback, a
custom cover design, and distribution to 25,00 retailers.  Join our almost
10,000 published authors today. http://www.iuniverse.com/media/techwr

  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.