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 just ignore the discussions on grammar unless it involves my job.
But the truth of the matter is that Tech Writing covers so MUCH
A) You'll never be bored.
B) There will always be at least one part of Tech Writing
that is a real pain.
Hey - nothing's perfect.
I also have to agree that Tech Writing involves a certain amount
of tedium. You _have_ to focus on the details and get them down
right. For just one example, I'll sometimes spend 45 minutes
writing one paragraph just to make sure it's technically accurate.
And, of course, the reader just skims through it and says "Oh.
Good writing should be so clear that it's obvious. But it can
take sheer brute force and tedium to get to that point in the
first place. Not always. Just sometimes. Still, we do it because
(pick one or all):
o We're committed to writing
o We love it and want to communicate
o We're insane masochists
I second Murrie Burgan's summary. We can be tired, exasperated,
and ready to pull our hair out - to which I'll add "about ready
to shoot someone".