Re: doc release

Subject: Re: doc release
From: "John Posada" <writer -at- tdandw -dot- com>
To: <wswallow -at- nycap -dot- rr -dot- com>, "'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Sun, 18 Jan 2004 19:06:15 -0500

Hi, many situations, you are correct. However,
keep in mind that there are all types of tech writing
assignments. Take my previous one. I documented two major
back-office systems behind the web...stored procedures,
processes, COM+s, databases, XML schemas, triggers, EAI
components, etc.

Things were ALWAYS changing...a database table is added or a
row is added to an existing table, a server IP is changed,
an upgrade to a stored proc trigger is deployed, a modified
XML schema is released. There is no deployed
application...there are 100 deployed applications. Every
day, something is deployed. It may be a X.0 release, it may
be a 0.X release, it may be a, 0.0.X release to any number
of softwares, modules, applications, tools, DBs, COMs, VB
scripts, etc. Tell do you even approach a freeze, a
snapshot, or even a delta? You simply evolve the documents
as the environment evolves.

John Posada
Senior Technical Writer

----- Original Message -----
From: "Bill Swallow" <wswallow -at- nycap -dot- rr -dot- com>
To: "'John Posada'" <writer -at- tdandw -dot- com>; "'TECHWR-L'"
<techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Sunday, January 18, 2004 1:36 PM
Subject: RE: doc release

> 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?).

RE: doc release: From: Bill Swallow

Previous by Author: RE: Abstract Design Document
Next by Author: RE: Best Word trick I've learned this week
Previous by Thread: RE: doc release
Next by Thread: Re: doc release

What this post helpful? Share it with friends and colleagues:

Sponsored Ads