Re: Culture, or What it means to be a Technical Writer

Subject: Re: Culture, or What it means to be a Technical Writer
From: Bill Swallow <bill_swallow -at- ROCKETMAIL -dot- COM>
Date: Fri, 8 May 1998 08:33:36 -0700

> User documentation is the whole package, not just the written word,
and
> everything you listed is part of the "translation" process, in my
mind.
> You can't "translate" something if the end result isn't understood by
> the person you are translating for. User analysis, selection of fonts,
> style, graphics, terminology, layout, binding, etc., all have to do
with
> how useful the end product is to the user.

So then what I think I'm hearing is that we are now having the same
problems defining "translation" as we are with "technical writer".
So, where do we go from here? Do we continue to analyze and
over-analyze until we're all blue in the face and sore in the fingers?
I forget who said this, but kudos to him/her... "I explain to people
what I do instead of telling them my title."

Well, now back to my tech writing/translation/information design and
management/and so on.

===


Bill Swallow
bill_swallow -at- rocketmail -dot- com
http://www.geocities.com/Heartland/Park/4353


Courage is the complement of fear. A man who is fearless cannot be
courageous.
-- Robert Heinlein

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com




Previous by Author: Re: Culture, or What it means to be a Technical Writer
Next by Author: Re: Culture, or What it means to be a Technical Writer
Previous by Thread: Re: Culture, or What it means to be a Technical Writer
Next by Thread: Re: Culture, or What it means to be a Technical Writer


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

Sponsored Ads


Sponsored Ads