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.
Mine is almost the same, except that I agree with some of the sentiment.
The manuals I work on, which are mostly revisions of pre-existing manuals,
are exceptionally technical and dry; I'm not surprised when someone says
the clients never read them. The two manuals I've created myself are half
the size of their counterparts, more direct, and have far less text and
more illustrations. What little feedback I've received has been good.
"Infodumping" is a problem. The guys in tech support, sales, and software
often want me to include "one little thing" which becomes another page. Or
two. Our five.
This has been bugging me for months. There has to be a better way to do
this, to streamline the documentation to the point where the user isn't
afraid to open the manual.
Of course, I'm biased. I was an arts (film animation) major.