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.
> More than once I've seen a user's question answered with "As stated in
> [name and date of document], . . . " -- in other words, "hey, look it
> up next time instead of bothering us with a question we've already
> answered!"
> Ouch. Benign-looking words, but in context they're a rebuke.
I had my company's Customer Support people trained to answer support
questions in just that [first] way.
Those who are thin of skin will take it to heart, and be too embarrassed
to make a fuss about having failed to use the resources provided.
Otherwise, they'll helpfully and righteously point out where/how the
navigation breaks down, and we'll humbly thank them, and fix it for the
next release.
Those who are thick of /h/e/a/d/ ... er... skin, will not even be able
to hear the implied criticism, since criticism could not possibly apply
to them. It's like the aural equivalent of the fovea.
