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.
> Um... you *may* want to make that your mantra, but you'll soon lose the
> cooperation and respect of the very programmers you need to make the
> changes you want.
> The best UI designers I've worked with have been programmers. I feel that
> I as a tech. writer have a great deal to offer the programmers to improve
> the UI, but any claims that I and I alone represent the users would
> deafen the programmers to any suggestions I had to make.
What Alan is saying is that programmers think obviously more about the
technology and doing so they organize the interface so that it fits the way
the software is built instead of organizing the interface so that it fits
the way the users work.
Having a techwriter suggest another word here and there has a positive
impact on the overall quality of an interface but a way bigger impact could
be had if the interface were the responsibility of a non technical person.
Working with programmers to design an interface is like working with inmates
to design an asylum. They have their own not so hidden agenda.
See "The inmates are running the asylum" by Alan Cooper.