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.
Subject:RE: A technique to get on development's good side From:"Daniel Pitre" <dpitre -at- guarded -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 13 May 2005 12:54:57 -0400
Gaff #1: "laying claim" NOT "laying clam"
Subject: Re: A technique to get on development's good side
This is my first post, so if (or when) I make some gaff, please let me
know and I'll immediately recant, beg forgiveness and generally show
remorse for my erroneous ways.
That said, I would like to chime in on the "getting on dev's good side"
topic. It is my humble opinion that often those who are "Technical
Writers" are perceived to be lacking in one (or both) of the domains of
expertise the title indicates. Developers maintain a high level of
proficiency in their domain of knowledge, and expect that those around
them will have a clear understanding of the underlying principles before
laying clam to knowledge. The measure of a person's worth in a
Development organization is their perceived level of knowledge and their
ability to contribute to the solution. I have found that an honest
assessment of your level of technical knowledge and a frank and open
dialog about your strengths and weaknesses will win out over posing and
pretending to be the expert. Content trumps style until the cows come
home.
In short, technical knowledge should be an ongoing project for every
"Technical" writer. The best developers never stop learning, and if a
Technical writer wants to gain "street cred" with them, join in.
I know this is lengthy and pointed toward those who were not previously
"developers". But it's an opinion, nothing more...and nothing less.
Thoughts?
"Woe to you, scribes and Pharisees, hypocrites! For you tithe mint,
dill, and cumin, and have neglected the weightier matters of the law:
justice and mercy and faith. It is these you ought to have practiced
without neglecting the others. "
New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
