Re: This too is technical communication

Subject: Re: This too is technical communication
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 1 Jun 2007 13:29:48 -0700

In most of my working experience it is relatively rare for developers
to be the ones who define products. More commonly, there are
marketing or other product people whose job it is to understand
their customers' needs, determine what kind of a product would
be able to meet those needs and predict what the potential revenue
to be made from such a product would be. The developers are
tasked with the goals of initial research to determine if the product
can be created, and only when it is concluded that it can be done
at a cost that will result in profit from the predicted revenue does
development happen. In my previous career as a test engineer I
think I atually worked on more products that never saw release
than ones that did. It is only in recent (say the past 15-20 years)
that whole industires have grown around the model that some
techie comes up with a "cool idea" and others throw money at
developing it into a product or service on the hunch that enough
people will think it is "cool" enough to spend actual money to buy

Gene Kim-Eng

----- Original Message -----
From: "Lauren" <lt34 -at- csus -dot- edu>

> Did I get lost here? Arhitects, information or otherwise, create the
> blueprint for some product, whether it is a building or a technology system.
> The product does not exist until it is defined and built by developers.


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual:

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-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

RE: This too is technical communication: From: Lauren

Previous by Author: Re: Technical writing for finance: one for the Friday files
Next by Author: Re: This too is technical communication
Previous by Thread: Re: This too is technical communication
Next by Thread: Re: This too is technical communication

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

Sponsored Ads