TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I would certainly never suggest that. I would say that
knowing what the user knows (in addition to your doc
skills) is the *minimum* you need to attain credibility
in the eyes of most developers (and I've know more than
a few developers who would view a writer who knows that
much as being better than what they've had to deal with
in the past). Everything else you know about the subject
makes you better, so long as you don't let it cause you
to forget that the user doesn't already know it. It's
what makes the difference between looking at someone as
if they could probably do the job and seeing someone as a
highly valued member of the team who you'd want to make
sure is included in every step of the process.
------- Original Message -------
On Mon, 1 Mar 2004 12:41:18 -0500 John Posada wrote:
>Why must it be that we can only write for the user
>if we're as uninformed as the user.