> People like this get grumpy and sulky when the technical decisions aren't what they agree with. They might even shout or yell at other people to get their own

> People like this get grumpy and sulky when the technical decisions aren't what they agree with. They might even shout or yell at other people to get their own > way. They'll deride the technical opinions of their teammates so they that can be "right", and "the winner" of the technical point in question. This seems like someone who is not making technically correct decision but still wants to be the winner. In this case, I actually think it's good that people would fight such stubborn people who are not right and still want to have their way. There are a ton of those kind of people out there. > They value "the right technical decision" over human relationships and it doesn't seem to occur to them that the right outcome might be the one that makes > > > someone else happy, or is the most diplomatic, even if it isn't "technically right". This sounds like the case of ethics. Do you work to make someone happy or do you do the right thing. I both the two cases, technically correct decision should be the way to go. Otherwise you are compromising work ethics and then you get into the ugly office politics arena where you are only working to make people happy without caring about the architecture, tools that could benefit the software. I might be a difficult person few years back, but today I give up and see that not many people are passionate about software as I am. For many it's about family, progressing their career and not about software and its users, which is what it should be. I have also come across a lot of people who have tried and succeeded in making the wrong technical decisions and still got the promotion. After nearly 10 years, I think software industry has become an ugly place because now it has too many people who are pseudo software lovers.