Slashdot Mirror
Abused IT Workers Ready To Quit
An anonymous reader writes to tell us that new research is suggesting as many as a quarter of all IT staff in small to medium businesses have suffered some sort of abuse and are looking for careers elsewhere (PDF). "The study also found that over a third have suffered from sleepless nights or headaches as a result of IT problems at work, while 59 percent spend between one and 10 hours a week working on IT systems outside normal hours. ... The biggest cause of stress among IT staff is problems arising from operational day-to-day tasks, the survey found. Another major cause came from loss of critical data, according to Connect."
59 per cent spend between one and 10 hours a week working on IT systems outside normal hours.
That's the problem right there: in IT, work can be endless. Saying no is key to keeping your sanity. But 2009 is not the best year to take risks. Good luck finding a job elsewhere.
It's bad in IT, but at least you get to use your brain (to some extent) and some of it is sometimes fun. That's a start.
Do fun stuff on the side and keep your skills current. That could become very handy sooner than you think.
--
FairSoftware.net -- the community for fair entrepreneurs
The number of BOFH increased significantly in 2008.
These 'small and midsize' businesses don't have the staff to hire a DBA, a sysadmin, a helpdesk guy -- you're it. You're the jack of all trades.
It's rather logical to think you're going to get abused, because the same person who is fixing SQL queries is now known to be the helpdesk guy, and unfortunately can't keep up with the work.
That said, I've been there. And working 80 hour weeks, I had enough, and moved to a large, massive corporation with good job deliniation. Not only do I learn more because I have the time, I work 40 hours a week (barely) and make far more money with better benefits.
Just a reminder folks, work to live, don't live to work. There is no such thing as a 'dream' job, because at the end of the day you'll always want more, best to find a job that allows you to live your life to the fullest and provides you a good salary as a bonus :)
Cheers and good luck to those out of work in '09, it's shaping up to be a tough year.
The price is always right if someone else is paying.
Like the post office or public education...it never stops.
Unlike those examples, it never pauses. Face it guys...you are babysitting. Networks, servers, desktops, whatever... IT is babysitting. And this baby always needs sitting....
Instead of quitting in an "employers market"... try something like Gracie Jiu Jitsu... choking a motherfucker out makes me feel better after a day of IT BS.
On the bright side, we'll all be up shit creek when we use all the fossil fuels. At least your servers won't need babysitting anymore.
THL phish sticks
"But it is hugely disappointing that, all too often, this has led to them being verbally or even physically abused.
They fired me! They would spank me, and would respond with "Faster! Harder! Tell me how I've been a BAD BOY! Tell me that I'm a filthy little whore!"
That's when they discovered that I was a masochistic pervert and canned me.
While it is not the full problem. But the common Ego among IT workers exasperates the problem.
The I am smarter then everyone tone, you are stupid because you don't know to run the app nested in the menus of the start button. Without me this company will collapse. Type of ego.
A lot of the time working those extra hours are voluntary, but because you think it the collaps without you, you do the extra hours.
The I'm smarter then you, makes sure your boss doesn't feel bad about letting you go, or pushing you that much more.
We don't treat our selfs and others like humans, so why do expect other to treat us so.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
And at the very end of TFA:
"Ten per cent of the companies surveyed said they had lost critical data through backup tape failures."
Is it just me, or does 10% seem like a huge loss rate?
/Test your backup
[Fuck Beta]
o0t!
Yeah I'm talking to you. The wannabe computer programmer who thinks they are good at computers because they can click around the computer enough times and find the reboot button and 'fix' an inherently flawed windows system. You think you're cool because you can pirate photoshop but not know anything about it, get Microsoft Office for free but have the literacy of a 1st grader when writing a paper, and get a copy of Norton Anti-virus because your inherently flawed system is useless without Administrative privileges. Get a clue, you are not smart, you are just a corporate sheep for a company that will bury you if you ever tried to write any software that did anything remotely useful. You are a clickaround and all you know is your ugly gray existence that is Windows.
Want the source code to windows vista?
head -n 1000000 /dev/random > Windows.com
And why do doctors and lawyers "put up" with working lots of overtime? Could it perhaps be because it's more of a choice and because they actually get some serious compensation for it? I seem to remember some article a while back about a doctor who was found to have endangered his patients by working way way too much, and his reason was summed up as "I wanted to buy a new boat"...
/Mikael
Greylisting is to SMTP as NAT is to IPv4
The IT manager Book of Abuse:
* cat-5 strangulation
* bayesian water torture
* physical loopback devices
* burning and branding
* PROFIT!
The biggest cause of stress among IT staff is problems arising from operational day-to-day tasks
In other news, doctors get stressed by having to do clinicals, and retail workers get stressed out by daily customers.
Convert FLACs to a portable format with FlacSquisher
Managers who expect that data will never be lost, yet are unwilling to authorize equipment purchase and hours required to install and maintain a proper backup system.
The real "Libtards" are the Libertarians!
1 to troll in 2 seconds...
Honestly I think this acceptance of things going wrong and "thats just the way IT is" belongs in the Windows world.
I have personally quit 2 jobs in the past because I was asked to work with Microsoft products.
User friendly and sysadmin friendly are two different things.
Sorry to troll but this is from the heart. I'm not that big but I will straight whoop that ass if someone attempts to phsically abuse me in the workplace. Maybe I'll lose, and if I do I'll be back to jack up your car.
"I guess I'm gonna fade into Bolivian."
I hijack supertankers for ransom. It's fun and pays really well! Back in college, I never would have guessed those Somali language courses would end up being so useful.
While I don't condone abusing the incompetent, we have been doing our own source code repository backups in engineering, since IT admitted that they cannot recover the repository from backups. We can't recover the repository either, since IT "owns" it, nor are we permitted to use an alternative, but we do incremental and full backups regularly of a "latest" sandbox, and at each release tag, so we can reconstruct the data set.
We have a Linux development environment, but those systems are hobbled by a Windows-centric IT shop that has firewalls blocking access to Google from non-Windows systems and Linux-centric forums everywhere.
This level of incompetence is typical of IT at many small-to-medium (once, even large) places I have worked. Mordac(s), the preventer(s) of information services, work(s) at too many places, and I wouldn't miss them if they all quit and got jobs where they could be useful.
Yes I work in IT I think TFA was referring more to the personality type that migrates towards the IT jobs being nerds. Thus being nerds IT types tend to take abuse rather than standing up for themselves. If someone is being abusive they are probably just stressed out themselves. If it happens where I work I just quietly walk away and they are usually falling over themselves to apologize later(so I will come back and fix their computer). This is not because of some god complex. It is because I treat everyone in our diverse workplace with respect. So I demand it in return. BTW I have thick skin so it takes a lot for me to walk away but I will.
"The stupid neither forgive nor forget; the naive forgive and forget; the wise forgive but do not forget." -Thomas Szasz
There is a severe lack of respect for IT; a number of comments in here are unexpectedly examples of it.
IT work can be easy. IT work can be hard. IT is generally very time consuming; whether it be easy, or difficult.
I've done the gauntlet, from network drops, router configurations, firewalls, server installs, application suites, application development, end user training, requirements gathering. In the end the biggest problem is that everyone seems to think everything takes only about 10% of the time it actually takes. They see that one instance when everything goes right and decided that it must always be that fast and easy. It seldom is.
God complex? You must be in a small shop where the "experts" always say "I'll do it" instead of explaining to the new hire how things work, which helps them keep their "know it all, do it all" facade intact. Most large shops have people who are more willing to help others by explaining how things work, DON'T copy corporate secrets to their USB drives, and try to make things easier for everyone. Emotional? Sure. Stress makes people want to become emotional. Whiny? maybe on some message boards, but most of the IT people I work with are stoic, in person. If ANYONE reads another employees mail, unless directed by corporate security or HR, will be fired if caught. I imagine most other large businesses have similar policies.
As someone who migrated away from a direct IT job to an HR job that is tangentially IT related,...
All the babes work in HR!
some people forget that a good number of IT workers are exempt from over time pay.
The terminology tells how bad it used to be: "interns" used to not leave the building. "Residents" lived there but were allowed to leave during time off. "Attending" physicians actually lived elsewhere and came to the hospital. Those are not the conditions these days, but ask a resident you know how far it really is from the truth.
I'm a computer science academic, and so our department at one point got the brilliant idea that they could save money by greatly reducing the IT staff. After all, computer scientists have PhDs in Computer Stuff, so can run all their own IT, right? It turns out not really---and even when they can, it'd be a full-time job to do so, and they already have other full-time jobs (like writing papers and research grants and teaching classes and supervising grad students).
What's kept the whole thing running at all is that the reduced staff has two really excellent people who manage to pull things together, both of whom are much much better at their jobs than any numbers of CS PhDs would be at that job, because being a top-quality IT staff member and being a top-quality CS researcher just aren't the same job.
I suppose the change has sort of increased the respect the IT people around here get though: you definitely notice all the stuff that used to Just Work after the IT staff gets canned.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
TFA is pretty thin. IT people are stressed due to the... economy?
/bias - Sysadmin in a medium-sized company/
Rant begins>
What's driving me mad at work is dealing with buzz-word spouting idiots. They can barely spell "computer" but they'll come with requests that I perform some half-witted change to fix a problem that they created. (that, of course, won't work)
If they could just summon the brains the come to me with a goal (i.e. we want the application to run faster) I could fix their problems. Instead, I'm not allowed to address the garbage they've created for themselves so they can avoid looking as clueless as they really are. And just forget about introducing new tech to make everyone's life easier. They'd have to learn something new. That makes me a bad guy, until we NEED that new tech, in which case I'm a slacker for not having already done it!
And, no, I'm not perfect, but when I make a mistake I admit it and fix it. Meetings are a lot shorter when you say "yeah, that was my mistake. Sorry about that. I'll fix it" instead of blame-storming the issue for an hour or two of my life that I'll never get back! FUCK!!! FUCK!!! FUCK!!!
So I guess I'm saying, it not the job, it's the people. In the end, it's way less stressful to lower yourself to their level and play the blame-game instead of trying to achieve something useful. Note: this drives you insane if you have a brain. Never forget:
- no good deed goes unpunished
- if you fix something it's your fault that it broke in the first place
Anyway, that why I think about quitting 5 times a day. Unfortunetly, now is not the best time.
Note: there are some rare semi-competent to competent people out there who can at least partially do their job (whatever it is). They are no problem to deal with at all.
What I do in such situations is to record my unpaid hours, and then at the end of the year when the workload slows down, take off that number of hours. So I might get paid 40 hour salary, but only work 19 hours that final week before Christmas, due to the fact I had 21 hours of unpaid work back in August.
BTW if you are getting paid $80,000 salary a year, but your dumb boss has you working 80 hours a week, that means you're only getting $20 an hour. You'd be better off becoming a factory worker or truck driver where you can earn $25-30 an hour, and the job is easier.
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
That most people I know who work in some form of medical profession or in various "legal" roles work overtime because they want extra disposable income while most people I know in IT work overtime because it's that or "You're incompetent and lazy".
/Mikael
Greylisting is to SMTP as NAT is to IPv4
How many of those IT people are not truly qualify to handle the positions they are in? While many IT people are extremely competent there are many, many who are not. Seen some IT people spends hours and hours trying to get something to work, the competent Joe IT fixes it in five minutes.
"But I am MCSE certified! I know exactly how to do it."
Half of writing history is hiding the truth.
I find a lot of folks in the IT trenches tend to be reactive rather than proactive.
They seem to enjoy being the "goto" guy that saves the day by resurrecting the server with the melty motherboard and toasted power supply while hundreds of users anxiously sit by their desks in breathless anticipation. Merely, switching to a failover server would never be as rewarding.
They regale in bragging to their co-workers and more importantly, their bosses about how many hours they spent rebuilding databases and applying emergency kernel patches at 3 am.
Face it, what kind of attention do you get when your servers never fail? When you never lose a database?
Nothing.
Skip ------ See the latest from http://www.anArchyFortWorth.com
If someone did that to me, my first call would be the police, and my second call would be a lawyer. Physical assualt is NEVR acceptable, and the person who gave me the black eye would be paying the price for his stupidity.
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
And IT is still the industry that refuses any form of unionization. Everybody is too smart and too privliged because of the technicality of what they do to see the benefits of working together to make things better for us.
And before you start flaming, think where you would be if you were actually on your own, if you had to code your own OS, compiler, library and every other piece of software you use in your job. Yeah, but you are a lone wolf. Keep it up IT
At least they do for a certain type of personality.
While you are responsible for EVERYTHING, that means that you get to set up everything the right way. Your way. If there's a problem, you can fix it the right way.
As long as you can put up with the salary and hours, the job should be a cake walk.
Cars are far more reliable. I drove my Dodge Shadow 340,000 miles which is the equivalent of 7000 hours operational time, and I can count on one hand how many problems I had with it. (Brake rotor failure, spark plug failure, leaky radiator, failed emissions, and that's it.)
In contrast computers seem to have a problem every 50 hours (once a week) of usage. That's why people get frustrated because they think a computer should be more like a car with 1500 hours between breakdowns (once a year).
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
Man are you clueless.......
Your comments reek of a know-it-all ego. First off you speak like all in IT have an ego. Farthest from the truth.
I will refute your anecdotal evidence with some anecdotal evidence of my own.
I used to be in IT. Specifically, I was a programmer. It felt natural and fun and really stroked my own inherent nerdiness. (Additionally, it was a way to insulate myself from having to be in uncomfortable social situations, but that's not really germane to the subject at hand...)
I left IT last March and have since been in sales. Now I spend much of my day talking to strangers on the phone. In other words, I am doing cold-calling. How am I doing? Well, the web app I wrote that tracks the results of my calls tells me that I have made 4063 calls since then with 703 conversation with "decision makers". Additionally, I have only had one person hang up on me.
It is a very, very, very different world here in sales. It's touchy feely, talky, and decidedly NON geeky. Well, there is a slight geeky side to it, but it's psychological and thus a "soft science". So I don't consider it to be true geek.
Where is this going? Well, since I'm doing b2b and providing a technological service, I occasionally run into business owners who tell me, "Our IT department handles that, you need to talk to them." I have to tell you, that's poison to my ears when I hear that. Why? It's because IT workers view me unconditionally as some stupid uppity sales weasel who knows nothing about technology and deserves to be looked down upon. I think this is partly due to the fact that by adopting my service I would be depriving them of a job, but moreso because they view themselves as the master of their domain and don't like to be educated.
And, honestly, I empathize with them. If I were in their shoes, I would view me as a stupid sales weasel. This is partly because I deliberately sound stupid on the phone (it puts business owners at ease -- there's that "touchy feely" stuff), but moreso because being smart and competant is very much part of IT culture. I remember feeling like I had to compete against all the other IT workers in my job. My brain power was my currency and my dick size in the IT world. I haven't ever worked an IT job that wasn't like that. You have to be able to build up a defensive barrier to survive in that kind of environment -- where all of your peers are going to try to show you up with their brain. You have to be ready to show them that they're wrong and know nothing.
In fact, isn't that what you did to the Parent by telling him, in essence, "You know nothing of what you speak, moron!"?
I also talked to my sister about this, since she works doing sales for web services in the UK. She shares my opinion, calling IT workers "smug" and "condescending". And she's right. I think IT workers and trained to be that way by their peers. If they have to be ready to defend themselves against their peers, how much respect do you expect them to have for some slimy sales weasel who makes much more money than they do and never has to think about recursion or race conditions?
But it still sucks when I have talk to an IT worker the phone.
I'll also add that my many phone conversations have allowed me to gain several levels in Wetware Hacking, which is fun.
I don't make the rules. I just make fun of them.
I have personally quit 2 jobs in the past because I was asked to work with Microsoft products.
Pshaw.
I quit an all-Unix shop when I found out my boss used emacs.
Burn, infidel!
I don't make the rules. I just make fun of them.
My bit of advice, from a former chronic "all nighter".
Don't sleep at your desk. Find a spot to catch those 2 or 3 hours of sleep before sunrise.
I preferred to sleep behind the big environmental units (AC + dehumidifier). The loud buzzzzzz of the unit was a lullaby to me. And sleeping on the floor was better than sleeping in a chair head in arms on desk, neck pain ow.
You mentioned illegal. Are you working on an H1B visa or something?
The cost of that cleanup, of course, will be borne by taxpayers, not industry.
I work in a medium sized business, where I am the only full time IT staff. And your generalizations are still way off.
I'll grant you that there are a few that act that way, and they do tend to get the lion's share of the spotlight, but most of us enjoy the unique challenges the small/med sized business presents. And yes, I have worked as part of the large, mammoth organization as well.
I enjoy the variety you get from doing a little bit of everything. I enjoy having to learn about new technology and how it applies to us. I get to plan out our over-arching IT plans, and be in the trenches implementing it. I enjoy teaching users how to use the technology given them to improve their own working abilities.
What I don't enjoy are the small but very vocal handful of users who allow their frustration at their inability to understand some bit of technology to carry over to an immediate and irrational frustration at me. Luckily, I view these, too, as another challenge, though a more long-term one than most, and have managed to convert a number of them into, if not eager, at least willing learner.
Now, I'm not going to say right off the bat that you fit that category; I'm willing to give you the benefit of the doubt and assume you've just been exposed to the minority IT group mentioned above. But how about you cut the rest of us hard-working stiffs a break, ok?
For the record, most users I support WANT me to be able to read their e-mail, to pull up what their current password is, and are surprised when I state that, for security and auditing purposes, I can't do that.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
You can't always say no.
I literally was up until 3:30am last night. During that day our SAN's SPS went offline and as a result, write cache was disabled on our SAN. This affected our file server and it would lock up, resulting in users locking up.
So I had to stay up late with Dell trying to get it fixed. What would have happened if I had said no? I would have to deal with all the problems in the morning, and listen to it from over 100 users.
Sometimes you just can't say no. But to make matters worse, once you give your boss the notion that you will work outside of business hours, they will expect you to do it more.
Much like getting a business phone...When I first hit the industry, I thought getting a work phone would be awesome!...Now? Because I checked my email so much outside of work, they expect a response out of me when they send an email.
The greatest revenge in life is massive success.
My last job was of the better ones I had. We start out small, not IT related (env. engineering). The work was interesting, e got to rollout new technology. Since it was a smaller company we spent a large amount of time with the end-users getting to know them, their problems etc. We really developed a good rapport.
We not only set up the infrastructure (email, networking etc.) but as there was no software to do many of the unique tasks of the company (I would look about 2 times a year) we got to do some interesting software development.
I left for two reasons:
1) I became very interested in Hydrology and decided to pursue that. I wanted a job with some field work.
and
2) As we got bigger the principals decided to hire a "real" manager. Big mistake. Up until then we were shipping software every few months in small increments to improve work flow, finding ways to do tasks for clients so we could bill out hours and be largely self-funded and basically maintaining a positive atmosphere. Within a short period of time costs skyrocketed, billable hours disappeared, the environment became toxic, the rapport with clients deteriorated and the department began to show no results. I'm glad I got out when I did.
The upshot is, if you find the right company and can create a good environment it can be fun.
putting the 'B' in LGBTQ+
So why not just ignore him and get on with the job? If he complains then ask what else to do.
I'm looking over the postings here and have realized that the people who are saying that IT workers are whiners and should suck it up - they have never worked in IT and have no idea what it's like. It must be just like any other job, right? No, it's not.
It's a job where upper management sees you as a cost center; you contribute nothing to the bottom line. They don't want to spend any money on IT upgrades either; that old server has been working this long, it can keep on working for years. Problems? That's why we have IT staff.
When things are working you've got management wondering why they pay you. They are constantly finding busy work for you so that you're not just sitting there. But when something fails - be prepared to work as many hours as it takes to resolve the issue. And don't be surprised if you've got executives standing over you and berating you while you're trying to fix the problem.
Imagine (if you can) the Exchange server taking a crap (like they're known to do). The database is corrupt? No problem, that's why we have backups. Now, restore the last backup and while it takes HOURS to complete you get to deal with every asshole in management demanding to know where their email is and why you haven't got it fixed yet. It's a test and if you don't have the right answer you're out of a job. Too bad there's no right answer - good luck trying to think one up.
I survived for eight years doing this job for a major international corporation. Would I go back to it? I'm not sure; the money wasn't too bad but oh geez, the working conditions were awful. It's not the actual problems with hardware and software that get you, it's the problems with all those managers and executives that seem to think that nothing should ever go wrong because they have an IT department taking care of it. And when something does go wrong it's because those IT people didn't do their jobs right and should be punished.
For those of you who think that this is overstated - go get yourself a job in IT and see how you like it. After you've done it for a year or two let's see if you still think the people who have actually done it are nothing more than whiners.
No, unions do not prevent people from being fired for cause.
Pro-athletes, writers, directors, and actors can make vast sums of money, are rewarded for success and creativity, and yet are members of unions. There is nothing about unions that would prevent you from making that six figure salary and getting that Viper you've wanted since you were 16 - nothing.
Yes, sometimes unions make mistakes, and some union members are lazy. But who hasn't worked at a non-union shop and seen lazy people who manage to keep their jobs.
Enron. Worldcom. Bear Sterns. Morgan Stanley. AIG. CitiGroup. Big companies that probably managed to lose a trillion dollars between them. Therefore, big companies are bad, will never work, and should be eliminated. Hey, it's the same tired argument that get's used against unions.
Unions haven't driven a single job overseas. Not one. You can blame executive greed and "free" trade for that.
No, union workers in Detroit do *not* earn $71 an hour. That figure is a lie, created by adding up all the compensation paid to current workers and the benefit costs to retired members, and dividing that by the current number of workers.
You work hard, you get rewarded. That's how it's supposed to work in this country. Yet if the minimum wage had increased at the same rate as the rise in productivity from the American worker, it would be $19 an hour today. If it had increased at the same rate as CEO compensation, it would be over $50 today.
Union workers make at least 11% more in compensation, have more vacation time, have *much* better health benefits, and have much greater job security than non-union workers. You may think you can do a better job negotiating alone, but it's simply not going to be the case. Unless...
Finally, say you really are the hot shit you think you are, AND ignore point #2 above. If you really are 10x as smart and work 10x as hard as the next guy, you don't want to be a worker bee in any case - you want to be in upper management, where union rules don't apply.
They like to be stressed, over-worked, exploited, have no personal time and also appreciate being handed enough rope with which to hang themselves?
Guess I'm one of those guys (although a mere 80 hours/week seems a bit slacker.) On the plus side:
1. Stressed? Yes. But if I want a day off, I just take it. No one is counting vacation and personal days in any real way.
2. Over-worked? Sure. I get stuff done on time and with zero supervision: tell me what you need and it happens. Heck, half my time is spent browsing the web to get up-skilled.
3. Exploited? Hmm... I produce results, you pay me obscene amounts of money. I can deal.
4. No personal time? Maids, nannies, accountants, PAs, etc, fix a lot of this. True that I don't get a few long Sundays fishing with the kids, but I still have time to read them a book every night.
5. Hanging rope? Bring it on! I'm doing what I think is right, and if it ever gets to the point that management and I can't agree on the right course of action, I expect to be fired -- I'm happy to do tactical, but I won't do stupid. The few times this has happened in my career, I've bowed to the inevitable and taken a 20% pay raise at a new company.
The issue in IT, at least from my experience, is not about missing deadlines or other planning, it's about work that springs up suddenly or constantly. These tend to be because of many factors:
a) Budget: A lot of small or mid-sized companies can't afford a huge amount of redundancy. If a server goes down, there's not a drop-in replacement for it. If you're smart there are backups, but one still has to get them up and running.
b) Time=Money: a little different from (a) Time is money. In environments that require near 24/7 uptime, downtime means money lost, which means that you're required to get things up and running ASAP, whether it's 3:00pm or 3:00am. Often again going with small-mid businesses, you may be able to afford all the expensive resources to keep things up (this includes redundant staff)
c) Other People: Plan all you want, but when your development team's latest project breaks a server at 1:00am, or marketing needs a last minute push, or a million other things... and you're the only one who can update or fix a live server... you're going to get a call.
It's funny though, because my previous job in a union shop with strict hours was irritating in the opposite way. I wasn't even *allowed* to work overtime except with large amounts of paperwork, so that means cramming what you would normally do "after hours" in a rather open schedule in a small and very stressful "window"
Not all data loss is caused by incompetent IT staff. If the IT staff recommend a functional backup system but management refuses to shell out for it, there's not much that can be done.
In my 2 IT jobs over the last 10 years, it has been my experience that the majority of my stress on the job, is caused by incompetent co-workers.
The people that hire IT/CS staff rarely understand that continuing education is what differentiates great IT staff from poor IT staff. The people that hire IT/CS sometimes having a good understanding of the 'buzzwords' or 'skillsets' required for a particular job, but do not understand how rapidly IT changes, and how important it is to hire people that are self-motivated learners.
Most of my major problems and frustrations as a developer/sys analyst, comes from working with people that have just enough knowledge to complete projects in their area, but not enough motivation or additional knowledge to complete their projects in a way that eases transitions over time.
As time goes on, the systems become more and more tangled and difficult to work with, to the point that any new project declared by management is 10x harder than it needs to be.
I consider management part of the "co-worker" set also. Most managers of IT sub-departments (manager of network services, manager of data center, etc..) have enough knowledge to direct their employees fairly well in their own little kingdom, but rarely have an understanding of the "big picture" as it comes to the IT services as a whole.
The net result of these little ignorant "kingdoms" inside an IT department, is a very frustrated worker trying to implement projects which are often much more difficult because of conflicting priorities and resource allocation.
One of the stereotypes of IT/CS work, is that it is too hard for the average person to understand: it is 'mysterious'. This view tends to reinforce the idea that it is OK to not explain your IT actions, and just 'fix the problem'. Numerous uncoordinated 'fixes' often results in project delays and failures.
To sum up:
While I haven't yet seen an 'in production' way to make sure that the right staff are hired, and I have seen a few ways that address the issues of managers communicating, and ways to unveil the natural secret-like way in which a lot of IT work is accomplished.
The first a quick 15 minute "who's doing what next week" type meeting. Everyone in IT, as well as super users of all the systems, meets on a friday afternoon and just rapidly spills out what is going on. Standing meeting to keep it fast. Just a quick mention of the DETAILS of your work. Whether or not everyone understands what you say is irrelevant. The major purpose being to throw everything in IT out in the air and see if anyone else sees a problem with it.
The second helpful thing I've seen is to have a group of USERS, not IT staff, help direct the priority of projects. IT managers have to present their projects and justifications for those projects, and the users decide what is most important. You'd be surprised how well that works to bridge the gap between IT and its user base. Oftentimes, a user/superuser of your systems can be frustrated by a mysterious network slowdown, a service outage, or or or... Keeping them in the loop takes that frustration away, which keeps it off your day to day IT workers.
And the last good thing I've seen is to make sure that IT has meetings that span departments. Your desktop staff, helpdesk, developers, server admins, etc.. should all be meeting together to just 'shoot the shit' every so often. It is amazing to see what could have been big problems adverted by having a no agenda cross department meeting every couple weeks.
At any rate, none of the above applies to small IT teams, but it has, and is working, for our larger 100+ IT staff at the institution that I'm working for.
That was just beautiful, man. Just perfect.
The fact that you can demonstrate such an awesome grasp of this fundamental concept makes me want to vote you IT Czar.
Seriously. I want you to go all around the world and talk to absolutely everyone and repeat that little speech. I wanna see you show up as a guest on The Daily Show. I want to see them make "Backup Plane: The Movie" I want you to wander the Earth like Johnny Appleseed and Samuel Jackson in "Pulp Fiction," getting into adventures and imparting this wisdom to all you meet.
And then maybe, just maybe, on some faraway golden day, in a better world than the one we have now, I'll pick up my phone to hear some poor netadmin chump cry out for help and when I ask that vile bastard "Do you have any backups?" maybe, just maybe, he'll say "Yes, I took them yesterday."
And when that glorious day comes, ToasterMonkey, I swear I will find the tallest twin peaks in the world, and dynamite the first into the shape of a toaster, and the other into the shape of a monkey, in your eternal glorious honor.
He put his boots up on the table and made a face. "The sig," he smirked. "You can waste your life in search of the sig."