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.
> The
> "user-advocacy" concept assumes that you as a tech writer have some
> unique
> vision into the mind of users. The truth, you have no better vision than
> the
> next guy - engineers included.
Two things are wrong with this statement.
First, we have (once again) a sweeping generalization based on the
erroneous assumption that everyone here spends their days writing
instructions for hardware or software that was developed by engineers.
This is not true.
Second, the fact that the tech writer is a user advocate does not mean
the engineer is not. Don't go looking for slights that aren't there; it
only makes you look paranoid. ;-) In an ideal organization (and ideal
world), they should both be user advocates. In a bad organization,
neither is the user advocate. And in a *really* bad organization, they
*brag* about not being the user advocate (been there done that).
