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.
Then you must be blessed with colleagues who completely understand what you
do. I have not required developers to defend their code, but people who
thought they knew programming have done so. As writers we get way too much
of "well, anyone can write, so I think you should say it this way...". It's
not so much "defending" a writing decision as explaining to the non-experts
why one particular way of placing words on the page is better than another.
--Beth
-----Original Message-----
From: bounce-techwr-l-118812 -at- lists -dot- raycomm -dot- com
[mailto:bounce-techwr-l-118812 -at- lists -dot- raycomm -dot- com]On Behalf Of John
Posada
Sent: Tuesday, September 09, 2003 7:37 AM
To: TECHWR-L
Subject: RE: PHD in Tech writing
> was optional. I did say that one of the most valuable
> qualities in a writer is the ability to defend a
> writing decision, and that a
Andrea...having knowledge and skill of the subject means you won't HAVE to
defend a writing decision. I've never had to defend something I wrote. Why
should I? I don't make developers defend their code.
