RE: Developments in the review cycle

["Steve Hudson" <sh1448291904 -at- gmail -dot- com>]

> In online publication, whether that is a true hypertext or a
books-on-glass style PDF, there is no such physical manufacturing process
and so no need for a publication-wide definition or achievement of a
finished state.

Say what? New product ships, but doco doesn't need to be in a 'finished
state'? Sorry, completely disagree. May as well ship no doco, and whenever a
user somewhere selects help, a request is generated for some to be written.

Taking this a step further, why bother writing specs? Just wait until a
developer is stuck on a feature, or an end-user doesn't like the feature as
provided, and generate the need for a spec on the spot.

Yeah, no need for a finished state, so no need for an initial state either.

Steve



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives