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: More on Validating documentation From:Jim Shaeffer <jims -at- spsi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 25 Mar 2002 14:16:25 -0500
Kat Nagel wrote:
> success of a team had less to do with the attitudes of individual
> team members than with the overall culture of the company. If the
> company culture was goal-oriented and collaborative, then teams
> usually worked well. If it was a blame-centered culture, successful
> team collaboration was more difficult to achieve.
I think something similar accounts for my lack of frustration. The
people employed here tend to be task-oriented. Socializing with the
developers isn't even the answer. We are polite, mutually respectful
and can all laugh at ourselves. When something needs to be done, we
figure out who's the best person to do it and we all move on. (Some
days, this list provides most of my 'social' interactions.)
Then Bruce Byfield wrote:
> 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.
Lucky me. The customer focus of our developers sometimes puts me to
shame. It may help that each customer we have makes a major impact on
our bottom line and that our customers are demanding and vocal.
People who do not fit our corporate culture move on rather quickly.
Jim Shaeffer (jims -at- spsi -dot- com)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 http://www.ehelp.com/techwr
---
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.
