Subject:RE: This too is technical communication From:Chris Borokowski <athloi -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 1 Jun 2007 13:07:55 -0700 (PDT)
Not if they're part of a development team. The entire
debate has been misunderstood by some individuals,
yourself included, in that there's a vital
distinction:
1) User interface
2) Internals
Technical writers link user to goal via product. This
is where their information architecture skills come
into play, much as they do in those designing
enterprise apps.
I think many here don't understand that this context
is necessary to interpret the comments made, and so
have taken them out of context and drawn their own
conclusions.
--- Lauren <lt34 -at- csus -dot- edu> wrote:
> Technical writers document the product that exists,
> after it has been built
> by developers.
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel. http://travel.yahoo.com/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & 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 & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
