Re: How to deal with the conflict in your daily work

"Steve Berczuk" <[email protected]>
Newsgroups gmane.comp.programming.language-of-the-year
Message-ID <[email protected]>
Forrest (and everyone else),

This is just a partial answer, but I've learned a lot from reading
some of Jerry Weinberg's books, especially Becoming a Technical Leader
http://www.amazon.com/dp/0932633021

There are lots of other resources too if you want to learn strategies
for dealing with conflict and I'll guess that many people here have a
favorite book etc to recommend.

But yes this is an important, and often neglected, aspect of our work.
A lot of really good professionals take the attitude that things will
"work themselves out" or that emotions should not exist in the
workplace. Others think that there is "one way" to address issues, not
realizing that people are different.

What I like about Technical Leader is that Weinberg uses examples that
are very on the mark for software teams.

Good Luck!





On Mon, May 19, 2008 at 10:56 PM,  <[email protected]> wrote:
>
> Hi All,
>
>
> I know it is very big issue, not only limitted at software develop field,
> but also every industry field.
>
> In software field, maybe we often are pushed by the deadline, often faced
> with the bad bugs, often need to argue with coworkers,often ......
>
> so we have conflicts with coworks, with boss, even with family because of
> work......
>
> how do we deal with them ?
>
> So I just list several questions here , just to list some specific clues on
> talking this issue.
>
> What is the root cause of conflict ?
> How many categories ?
> What is the common strategy for them ?
>
>
> Best Regards,
> Forrest
>
-- 
Steve Berczuk | steve-Bvnk/[email protected] | http://www.berczuk.com
 SCM Patterns: Effective Teamwork, Practical Integration
 www.scmpatterns.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.