[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: It shouldn't be that hard to write good doc, should it?

Subject: Re: It shouldn't be that hard to write good doc, should it?
From: "Ed Wurster" <eawurster -at- hotmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 20 Jan 2004 07:04:15 -0500

John Cornellier wrote:
> In the course of a discussion about Pogue's latest Missing Manual the
> following question was posted on Slashdot: "I've often wondered why
> we don't see more books of this caliber hitting the market. It
> shouldn't be that hard to write good documentation, should it? What
> does it take?"

It takes:

1. financial commitment from a company,
2. allotment of sufficient time for the tasks, and
3. someone who can translate technical concepts.

Ed Wurster



Follow-Ups:

References:
It shouldn't be that hard to write good doc, should it?: From: John Cornellier

Previous by Author: Re: straw poll: do you type a command on, at, or in the command line?
Next by Author: Re: It shouldn't be that hard to write good doc, should it?
Previous by Thread: It shouldn't be that hard to write good doc, should it?
Next by Thread: Re: It shouldn't be that hard to write good doc, should it?

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

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

Sponsored Ads