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 have to disagree with John... Although "ship" is a bad choice of term, you
still need to freeze a snapshot in time in order to deploy the application.
If you don't, you have a nightmare of a system to maintain, or else
something that you always develop but never use (in which case, what's the
point?).
Bill Swallow
wswallow "at" nycap "dot" rr "dot" com
::: -----Original Message-----
::: > If there is no code freeze, when do you ship?
:::
::: Goob...not all technical writing involves projects that
::: ship. A large amount of writing is done for internal systems
::: that never ship, they just continue to evolve.
