Re: More on Validating documentation
Is there really no sense ofI've had good relations with developers far more often than not. However, I've noticed in many companies that developers are a community to themselves. I've seen startups fragment along the techie/non-techie divide. I've even seen CEOs and CTOs with strong programming credentials have to fight to win the respectof developers. Part of the reason for this situation may be geek mystique, the same kind of attitude that dismisses someone who prefers a GUI to a command line.
"we're all working together to make this overall product
as good as we can make it"?
However (and I say this with no malice whatsoever, just observation), I believe that the main reason is that many programmers really don't care about the product as such. All that they want to do is write interesting code. Finishing the product or meeting deadlines aren't major priorities to them.
Of course, not all programmers are that way. The exceptions usually wind up as team leaders or CTOs.
But, on the whole, developers are a closed community of introverts. By comparison, writers are extroverts. Therefore, as ill-equipped as most of us are by any other standard to make such an effort ;-), the writers are the ones who have to make most of the effort. They need to educate the developers on how to work with them, and have to make the efforts to be accepted.
Anecdote: since I started being involved with Linux, I've found that my relations with developers have improved immensely. Even if the developers aren't involved with Linux themselves, the fact that I've written articles about configurations seems to give me instant acceptence. When I mention my background, I can see the developers relaxing. Other people, with interests in some technical subjects have said much the same thing to me. I strongly suspect that gaining techie cred and letting it be known early in the relation is one of the easiest ways to get along with developers. It tells them that you are, at least faintly, one of them.
Bruce Byfield 604.421.7177 bbyfield -at- axionet -dot- com
"A river follows the path of least resistance, and that's why the river is crooked."
- Utah Phillips
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
- Re: More on Validating documentation, Tom Murrell
More on Validating documentation: From: Eric J. Ray
Previous by Author:
Re: Advice for a Canadian newbie contract tech writer on first contract?
Next by Author: Re: More on Validating documentation
Previous by Thread: Re: More on Validating documentation
Next by Thread: Re: More on Validating documentation
Search our Technical Writing Archives & Magazine