Should IT Unionize?
snydeq writes "Sixty-hour work weeks with no overtime or comp time, a BlackBerry hitched to your belt 24/7, mandates from managers who have no clue what you actually do — all for a job that could be outsourced tomorrow. 'Is it finally time for technology workers to form a union and demand better working conditions?' InfoWorld's Dan Tynan asks. To some, the odds against IT unions are long, in large part because the 'lone gunman' culture is pervasive. Diversity of skills and job objectives is another hurdle for rallying around common goals. But that has not dissuaded several union-minded groups from cropping up across the industry as of late, Tynan reports. In the end, the best bet for IT may be a professional organization modeled after the American Bar Association or the American Medical Association, one that could give IT professionals a single voice for speaking out on issues that affect everyone — such as H-1B visa limits or tax incentives to keep IT jobs onshore."
Well, gee, lets see. Setting aside the economic issues, the inertia and sloppy work that comes with systems where "seniority" is more important than "ability", lets talk about the Bar thing.
What does the American Bar Association do? Primarily it sets standards for it's members, and enforces them. Almost all professional associations do this, whether it's lawyers, accountants, or plumbers, you can't practice your trade unless they say you can...In Union strong states, you aren't allowed to hire plumbers and electricians who haven't jumped through the hoops, regardless of qualifications...Which is to say Joe Bob with his Master Electrician badge is more fit to wire your house than a guy with a PhD in electrical engineering who has 20 years experience in the field. Not only is he more fit, but you can't even hire the other guy because he can't get licensed without jumping through the union hoops.
Now, how many people get into IT through "non standard" channels? How many self-taught pros are there out there? How many people have a non-IT educational background? How many people from other countries?
Do you really want a bunch of senior people telling you what qualifications you need to have? This is a young industry, and it's changing all the time. What you need to know changes all the time. And they think setting up a professional organization is a good thing? Instead of clueless PHBs, we'll have 30 year vets telling us that our modern methods are crap compared to the work they did, back in the day, with punchcards.
Jesus. If you want to drive offshoring, that's the way to do it. Make American IT more expensive and less efficient than everywhere else in the world, and the work will flee this country and leave us longing for the days of H1-Bs and mere outsourcing.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
I don't agree with that assertion at all. In my experience, IT people are scattered all over the political spectrum. Sure, the libertarian types tend to yell the loudest, but the libertarian types yell the loudest everywhere.
Personally, I think unions are a good thing for a lot of industries. However, I don't think they're good for IT. Management in many places already see IT as nothing more than an expensive but necessary burden, and putting a union on top of that just makes the perception worse. In places where IT is seen as a vital component to the overall health of the company, techs tend to be treated much better.
The bottom line is that for most positions within IT other than the low-level button pushers, demand and pay are still high. However, it always has been and still remains to a large extent a meritocracy, so all the people who got into the field in the late 90s because they heard it was easy money now find themselves working the grunt jobs at the bottom of the totem pole with no hope of advancement. Unions may give these people opportunity to advance based on seniority alone, but doing so would be bad for the industry as a whole.
The current Indian Government pre-empted such a move by classifying IT as a "Profession", meaning no fixed working hours, no overtime pay, no benefits, but, we do need to pay close to $50 a year as Profession Tax.
Plus major indian IT cos have gone on record stating that long hours are simply "fiction" and each employee works only 8 hours a day: The last time i checked my team was working 14 hours a day.
"Doing what i can, with what i have." ~ Burt Gummer
...or comp time sounds like it's time to change jobs, not unionize. Unions correct for errors in the free market, and are not effective in situations where the market already has checks and balances in place. And in any case, there are few companies with large enough IT workforces to make unionizing a viable idea.
I think what you need to look at is the fact that IT jobs are becoming a blue collar skill. Just about anyone with a computer can pick up enough training to do the majority of desktop and server support work that the market demands. On-Site support for mission critical machines are increasingly being moved to co-location centers who have highly trained staff available. What this means is that there is an overabundance of workers in the field, thus decreasing the value of the service.
If you want to get more respect in the IT field, I recommend that you move to large data center work rather than desktop or small server support. Another idea is to develop industry-standard certification programs (not MSCE) that show qualifications for work in sophisticated environments, thus further helping differentiate desktop support from high-end IT support. These certifications would work a bit like the Engineering or Electrician certifications that differentiate true professionals from the trade-school material entering the field.
That being said, let me turn this thing on its head. Has anyone thought of addressing the reasons behind why you work 60 hour work weeks? Is it truly because the field demands it or is it because your environment needs improvement? Whether it be greater automation, additional help, or better procedures, you need to be making an effort to help reshape your environment so that you can accomplish your job more effectively. Not only will it help reduce the hours you work each week, but shaping your environment displays the true mark of a professional.
Javascript + Nintendo DSi = DSiCade
Ah, yes-- the siren song of unionization, born out of the early 20th century labor struggles where socialism was still an idyllic future utopia, and factory conditions were truly brutal.
Collective labor bargaining has a brinksmanship game at its very core: give us what we demand or we all quit. The problem is that this brinksmanship is all too easy to call bluff now: globalized workforce, wider literacy, part time contractors, etc. Beyond the obvious changes to the labor pool, the idea that IT work-- one of the most portable sectors in the economy-- could be unionized is laughable.
The AMA and ABA are possible because the inflow of labor is restricted from the beginning: one must graduate Med School or Law School from an accredited university. The AMA and ABA have very strict tests before one gets into these schools, and even harder tests at the end of them before they'll let you in the club. In that way, each association has monopolized the labor force by severely restricting membership. Would such a scheme be possible with IT?
An ITPA (IT Professionals Association) would require specific graduate schools and horrendous tests. The last thing IT needs is an officially ordained priesthood about what is IT and what is not IT. This would restrict the labor pool so tightly that businesses would freak out, the hopeful students would freak out, then the government, and the whole thing would fall apart before it got started.
I consider myself an IT professional, and I got my degree in Japanese Literature.
davejenkins.com |
I'm going to take a purely myopic, personal stance on this. I got into IT because I was interested in technology. I have seen more burnout and sacrifices by coworkers in this industry than any other. I have seen people responding to Blackberry messages at 2 AM (when they work 9 to 5), spend their days freezing their bodies slowly in server rooms and watched IT managers lose their hair trying to explain that "technology" doesn't mean "magic all the time" to executives.
I always thought there were worse occupations out there. Surely the garbage man or coal miner has a less satisfying/harder job than me. However, at the end of the shift, these guys go home. The garbage man doesn't need to pick up heavy cans in his living room. The coal miner doesn't need to chip away at the walls in his bedroom. In no other industry is the disconnect between work and life non-existent like in IT. Hell, even doctors have calling services.
The joy of learning new things was quickly squashed by the nature of this industry. Even when I'm programming or building new hardware, I'm connected to the responsibility of maintaining 24/7 systems on a 24/7 schedule.
I know some are saying "You don't need to have a job like this. There are other jobs in the IT industry that don't demand this kind of schedule." Bullshit. We brought this unto ourselves. We were the ones arguing for telecommuting. We were the proponents of portable tech. And now we have to "eat the dog food". We sold people on it, we have to bow to it ourselves.
I was thinking about this the other day. I'm almost 30. The internet came about in my generation. IT has been going on much longer. How was it done before "always-on", "always-connected"? Surely it was less efficient. And yet, you hear about IT people from that time staying in their jobs for decades, loving what they do, etc. Nowadays you're surprised to see someone stick around 3 years in a "permanent" job.
What did we do to our industry? How bad have we fucked it up? Can we change it by unionizing? I'll do anything at this point.
The UK has some very strong employee rights - but I would still recommend that anyone join a union.
I'm a member of Connect which is a specialist union for professionals in the Telecoms sector.
The way I look at it is like this: my employer has several floors of lawyers - how many do I have? I hope never to have to fight my employer for my rights (sick leave, working time directive, disciplinary etc) but if I do - I want a team of lawyers on my side.
I realise that the situation in the USA is different - the corruption and ties to organised crime that you see doesn't seem to have affected unions over here.
It's important to draw a distinction between "You can't do that - it's not your job" unions and "You can't do that to me - it's illegal" unions. The former are usually found with low-paying, blue collar works who have a vested interest in protecting their job at the expense of all else - including the company. The latter are usually composed of professional members who own shares in their employer and who want reassurance that should the worst happen, they're legally protected.
I view my union dues (less than £10 per month) on the same level as life assurance, building insurance etc. I don't want to pay them - but I realise it's probably a good idea. In fact, as well as all the legal help, my union also provide me with sickness and death benefit as well as good deals on general insurance etc.
Basically, if you think your employer is perfect and would never shit on you from a great height - don't join a union. If you live in the real world - sign up.
T
If a square is really a rhombus, why aren't all triangles purple?
I cannot think of a single thing that would make employers and customers abandon US IT more than if we unionized. We'd be signing our own death warrants. It's _already_ incredibly easy to fire up e-lance, and grab a Romanian and Indian developer, even if there are the quality and language issues. If we unionize, we'll only increase their incentive to do so by burdening them with all of the baggage that comes along with having unionized employees.
Unions rely on the ability to have a monopoly on labor (and violence, and backing from the government for their violence, but those aren't relevant to my point). With manufacturing jobs, where the physical presence of the employee is a requirement, their hold over an industry is far greater than it would be over IT services, since it's very very easy to utilize non-local labor that doesn't care about the fact that there's a union that went on strike.
Furthermore, I think that it'd be a straight up financially bad idea for almost everyone. In addition to making the barriers to entry for new developers and IT professionals higher, we'd all suffer in terms of the actual money we take home. Union contracts base pay around seniority, not productivity. In fact, most unions violently oppose productivity-based pay scales. That'd remove a lot of the incentive for new, young developers who are just _better_ than their older co-workers to excel at their jobs. They'd be locked into their pay level. It'd also make it MUCH harder to fire shitty employees.
I also reject the concept that there CAN be a single IT voice to represent us all. We're a fairly diverse group of people, from all backgrounds and with all goals in life. The incentives of, say, a sysadmin working for a NOC are not the same as a web developer working for a small business. They have different sets of priorities, both of which are completely valid to their particular situation. Say, for example, that the NOC guy is a little older, has some kids, and wants benefits, while the young kid doesn't care, and just wants as fat of a paycheck as he can get. How do you resolve those competing, equally valid desires? As it stands now, we negotiate our own contracts according to our desires. With unions, we'd be locked into the choices made by other people.
Another problem with unions, highlighted by this article, is that they're often ideological tools of the leadership. I don't have a problem with H1-B visas (except that I think they're too restrictive) or offshoring. I think both things are awesome. It's the market at work, and forces us all to be competitive at SOME level, whether that be on quality or price or reliability or whatever. Competing against a guy in India or a new Chinese H1-B immigrant is no different than competing against a college kid. The idea that we need political protection from that is absurd.
We also shouldn't ignore the negative impact that unionization of IT would have on the economy. You want to see the long-term effects of unionization? Take a look at the auto industry. Completely saddled with legacy labor costs imposed by union contracts, they're in many cases simply unable to compete on price. Unions are little more than mechanisms for imposing arbitrary minimums and caps on the costs of doing business, which decreases the flexibility of businesses when responding to changing market conditions. The only reason that Japanese automakers hire anyone over here is because we force them to by law.
There's nothing that a union can give you that you can't achieve for yourself by paying attention to your contract. Do you want a guarantee that you'll never be asked to work more than 40 hours in a week? Put it in your contract. Do you want cash instead of benefits? Put it in your contract. Do you want to get paid better? Don't work for less. You make the choices that you want to make, and don't impose them on the rest of us. We'll do likewise, and we'll all be happier.
You mean that I'd finally be able to afford a house there?
We already have an association: ACM.org
I had to quit the ACM because I could not ethically comply with their Code of Ethics:
First, I do not feel morally obligated to agree with EULAs, nor will I ever. If the law eventually says that they're binding, then I'll go along grudgingly, but I certainly won't voluntarily submit to hidden contracts.
Second, it is impossible to write a modern program without violating patents. Even if I believed that software patents are legitimate - and I don't - there are simply too many to avoid stepping on a few in all but the most trivial of applications.
I like the ACM in general, but don't support their core values. As such, I can't be a member anymore.
Dewey, what part of this looks like authorities should be involved?
I linve in New York, a union strong state. Here the only place you can't hire non-union labor for SOME job is in NYC. Most other places in the state where licensing is required it is called for by the municipality (town, or city). No one up here requires a union to work.
I've met people who are in the Manhattan electricians union who got there by non-traditional methods. They are truly skilled professionals.
What I do want is a bunch of senior people telling the company management exactly how long my shift should be, exactly when it starts and ends, exactly how much overtime I get for which extra days and hours.
Around here, in the Hudson Valley we have carpenters schools, steamfitters schools, I don't know how many union schools we have, beautiful campuses where the union membership goes to get their training updated regularly. Paid training in skills they will then get to use.
You know what the Teamsters still have that IT workers at Enron didn't? Guess. I'll make it easy for you. The answer is a secure retirement.
How do you explain all the IT offshoring that already happened? The overwhelming presence of the union? What drove all those call centers offshore? It wasn't the union.
Look, I know your 4th grade teacher told you that someday you would be rich and the schoolyard bully would work for you. They told you that a lot, that someday you will be the boss by right of your superior intelligence. Ayn Rand is wrong, sure you can excel on your own and protect yourself and what you care about and all that. If you want to make real change, and not remain insignificant, you need to be part of a group that has influence.
Here's a list of people doing well in unions...
Cops
Teachers
Truck Drivers
Carpenters
Plumbers
Actors
Screenwriters
Here's one more thing an IT union would be able to do. It could help define best practices. As in "Nope, that software is not union-spec. If you want our guys to use it you're going to have to pay for their training." Then the union membership (IT workers) would have some say over whether or not non-standard or poorly written software gets union support. As union members we would be protected from having the blame on us for every piece-o-shit software.
Don't focus on the abuses of power, that always happens. Can't not do something because someone might misuse it. Or do you not use filesharing?
From the reactions, I would say that most people here are against unions. I say, let us all take a stand together against unions.
Unite against Unification!
We'll form the Anti-union Union!
All those that don't wish to be part of a Union are now part of the Anti-union Union. Union dues are payable to me.
Great civilizations have lived and died on false theories. Don't mess up mine with a few facts.
Unions don't care about the people they care about keeping the Union strong.
1. They will agree to Layoff 100 High Paid and skilled programmers to hire 500 low paid and low skilled programmers. (as more people and more union dues and strong union)
2. They work on averages. On average Union employees do get paid more then non-union. However the trimming of pay cuts both ends of the bell curve. That includes getting paid more for a better job.
3. Less American Jobs. What Unions are suppose to try to keep American jobs? Yes but companies are smarter then that. Oh gee it looks like we are going forced to unionize... That is going to be a big overhead. Lets outsource now before the Union formalizes. Even if it does and a company can have enough infrastructure outsourced they can survive and thrive on the outsourced employees, or foreign devisions of their company as they strike for as long as they wont until they starve, give up, or get a new job.
4. Loss political power. You are Unioned and you are aligned with the Democrats. That means the Democrats don't need to worry about pleasing you as you will help them anyways as they focus on swing voters. And Republicans will see you as a hopeless cause and ignore you. Besides your voice will have to go threw extra layers of beurocrasy just to get your personal voice heard.
5. All Management hands are tied. Even the good ones. So they cant fire the bad employees and promote the good ones.
6. An other layer to please. You are no longer allowed to take the torch and get it done. As if you do too good of a job you make the poor employees feel bad and then you need to explain yourself to the union.
7. Unable to get outside help. Gasp hiring a consultant or someone else to help brings up the question what can this scab do that a Unioned employee can't. Heck for some jobs you need temporary people to do some work and then let them go when they are done. Hiring for Max productivity is stupid.
I will give them credit for many things they have done. But for many jobs they have outdone their usefulness. IT is too of a diverse area to Unionize.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.