Re: Re[2]: Release Notes

Subject: Re: Re[2]: Release Notes
From: Mike Stockman <stockman -at- jagunet -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 1 Mar 2000 13:53:59 -0500

On 3/1/00 12:41 PM, John Posada (jposada01 -at- yahoo -dot- com) wrote:

>It would be apparent that the user had thought about
>the document requirement, had identified specific
>needs, had applied that analysis to their specific
>environment, and was still having problems. Then, even
>if individual issues weren't addressed, I'd have the
>comfort to know that the person would even have the
>first clue about what to do WITH the information once
>I'd sent it.

Just to briefly expand on what you're saying, this is the same set of
skills that helps a writer Work and Play Well with developers. I've
worked with many, many colleagues who visit a developer, sit down, and
say, in effect, "Fill my empty head with information." Developers often
respond badly to this, and send those writers packing. (The writers then
go off complaining loudly to their friends about how difficult and
anti-social those pesky developers are...)

A writer who sits down with the spec (if there is one) and the product
(no matter how rough, buggy, or otherwise dangerous) and learns as much
as possible first will be welcomed with open arms by most (OK, far more)
developers than that lazy writer in my first example.

Just a suggestion to help people's efficiency.


Internet: stockman -at- jagunet -dot- com AOL: MStockman
AOL Instant Messenger: MStockman

Previous by Author: Re: IP addresses/domain names at the end of a sentence
Next by Author: Re: capturing clean screen images for book
Previous by Thread: RE: Re[2]: Release Notes
Next by Thread: RE: Release Notes

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

Sponsored Ads

Sponsored Ads