| Jerriji, I felt like I had to reply to this because I don't think your wrong, and in light of my last reply I think I may have come off the same way. "If you were poor and still are poor, then it's your own problem, just get out of my sight" I didn't take that away from the topic at hand. People unhappy in their IT jobs are employed and not poor in the Western world. So the unhappiness comes from something else. I've seen very well paid developers just fall off a cliff and suddenly hate their job. I don't understand the reasons, but I don't doubt that they are all that different from the reasons the rest of the working world faces. Sometimes it's time to change careers. As human beings, change is feared (or family obligations come into play that make accepting risk less desirable than doing a job you hate). I feel compassion for those individuals, but in as much as I have to work with them, my compassion is driven to finding ways to identify "great things" about the job they hate. Negative attitudes are poison and there seems to be a lot of that in IT. I can't tell you how many meetings I attend where the various stakeholders in our organization are at eachothers throats and my boss or me are called in to mediate. It's not an exercise of mediation, it's an exercise of breaking a cycle of frustration, taking the emotion out of it and focusing on the problem as the thing that gets the brunt of the righteous anger (it's amazing what happens when you take three pissed off people and focus their anger at the problem rather than at one another). Sometimes we're in departments that are only noticed when "nothing is broken" and are hammered on when some extraordinary circumstance causes something to fail. We resent the fact that the people doing the yelling don't understand how unpreventable that circumstance was. It's a tough roll to sit in and tolerate and breeds contempt. But focusing on that element of the job IS poisonous. |