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.
> IMHO, whenever I see poor technical writing it is my duty to my
> to notify the company from which it came. If they have a writer on
> should know their writing needs improvement (whether or not they are
> change it).
What unmitigated chutzpah! Who made you the arbiter of technical
writing standards? Who assigned you your "duty" to contact companies
and trash other writers' work? IMHO! In my humble opinion indeed!
How would you like someone who you've never met before to contact your
employer or your client and strongly criticize your work? How smug the
rationalization, "they should know their writing needs improvement."
If you are prospecting for work, and you see documentation that needs
improvement, contact the company. "You can use my services. I can make
this better for you." But to go out an destroy business relationships,
to go out and intentionally make people feel bad to satisfy your sense
of professional standing, -that will hardly raise the esteem of
technical writers in the world.
Rob McMartin has it right when he says,
> Don't bag the man who wrote the document unless you have sat in his
No one is immune to criticism. Even top-flight professional writers
can craft awkward sentences, and then display the blemish as a post
for the world to see.
Technical Writing Services
baruch -at- teleport -dot- com
-----BEGIN PGP SIGNATURE-----
Version: PGP 5.5.5