Slashdot Mirror


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."

36 of 1,141 comments (clear)

  1. Hell no. by SatanicPuppy · · Score: 5, Insightful

    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.
    1. Re:Hell no. by phlinn · · Score: 5, Insightful

      Oh for mod points. I agree wholeheartedly.. Can everyone say 'rent seeking'? I found it disturbing that the summary mentions 2 organizations who have gotten the law to explicitly protect them from competition as good examples to follow.

      --
      "Pulling together is the aim of despotism and tyranny! Free men pull in all sorts of directions" -- Havelock Vetinari
    2. Re:Hell no. by MyLongNickName · · Score: 5, Insightful

      I agree with what you said, except for one small nitpick. .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

      Joe Bob may be better qualified. Code changes from year to year, and I doubt an electrical engineer is going to be up one specifics of what gauge wire is appropriate for a given number of electrical outlets to feed, or how far the circuit breaker must be from the gas line. The electrical engineer undoubtedly would have a better theoretical understanding, but I would not want him wiring my house.

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    3. Re:Hell no. by SatanicPuppy · · Score: 5, Insightful

      Maybe, maybe not. The point should be whether or not the wiring passes code, not who does it.

      The thing that bothers me most is the exclusivity, especially with craft unions. There is no way in except through seniority, so if you come from a non-union state (or country) with tons of experience and ability, you're automatically a second class citizen in your chosen trade, and the only way out of that is having to jump through union hoops for literally years, maybe even under the supervision of someone with less skill and experience than yourself.

      As far as I'm concerned, the work is what's important. It all has to be inspected, so if it passes code, then what does it matter who did it in the first place?

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    4. Re:Hell no. by macshit · · Score: 4, Insightful

      Not to mention the idiocy of suggesting that everyone actually agrees on anything.

      I'm an American, but I know a lot of very smart foreigners working in the U.S. on H1-B's who make normal U.S. wages, and who are as good or better than their U.S. "competition". Given what I've seen, the constant whining on slashdot about H1-Bs has always seemed petty.

      --
      We live, as we dream -- alone....
    5. Re:Hell no. by jimicus · · Score: 4, Insightful

      Who do you suppose writes those codes?

      This is akin to saying "a bank manager would never be able to work as a loan officer because of the bank's constantly changing interest rates".

      A small group of electrical engineers of which your particular engineer may or may not be a member.

      Joe Bob's job, OTOH, is to keep up with what that small group write.

    6. Re:Hell no. by oldspewey · · Score: 5, Insightful

      I also would be against IT Unions--on the mere basis that (like SatanicPuppy said) my connections would outweigh my skills.

      Most times, union or non-union, connections outweigh skills anyhow. I can't count the number of people I've dealt with professionally who talk a good game, know all the right people, and fuck up 90% of the things they touch.

      --
      If libertarians are so opposed to effective government, why don't they all move to Somalia?
    7. Re:Hell no. by MyLongNickName · · Score: 4, Insightful

      Um..... no it isn't the same at all. If our PhD is in fact, the one writing the codes, then fine. In your example, it would be a finance professor stepping into a teller role for the day. He happily accepts a deposit of $25,000 in cash, not realizing he needs to fill out the appropriate "suspicious activities" form required by the government.

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    8. Re:Hell no. by Chirs · · Score: 5, Insightful

      It's possible for an electrical engineer to have very little experience with electrical power systems.

      I have taken several electrical engineering courses (have a degree in Engineering Physics) and have also done extensive home renovations (permitted and inspected).

      While the actual electrical parts of the NEC are generally fairly simple for most household circuits, there are many aspects to the code that are not simple electrical issues: conduit fill, thermal derating (which varies depending on the specific insulation type, wire gauge, and number of bundled wires), pigtailing requirements, box fill calculations, GFCI/AFCI requirements, mandated switch/receptacle locations, exceptions for heaters/furnaces/air conditioners, and all sorts of other things.

    9. Re:Hell no. by LynnwoodRooster · · Score: 5, Insightful
      True story... I was setting up my booth at the annual CES show, about 5 or so years ago, and was NOT allowed to plug my own equipment into power strips. Had to be union labor to do that!

      .
      Never mind that at the time I had my PE for the State of Nevada and was certified by the State to sign off on the wiring for the entire Convention center! No, I had to wait for some union stiff - at $50 per outlet - to come by and PLUG EQUIPMENT I DESIGNED AND PASSED THROUGH UL INTO AN ELECTRICAL CIRCUIT I COULD CERTIFY AS SAFE.

      I didn't really care for unions before that, but afterwards earned a healthy hatred for them...

      --
      Browsing at +1 - no ACs, I ignore their posts. So refreshing!
    10. Re:Hell no. by tzhuge · · Score: 4, Insightful

      I'm going to agree with you. As someone w/ an B.Sc. in Electrical Engineering, let me just say that I would never trust myself to wire my own house :) and I wouldn't trust most of my fellow students back in uni either.

      I have one classmate I would trust to do this right now, and that's only because he is big into car stereos and also has done contractor work before. Actually, when someone else asked him for some help with home wiring, he recommended that they seek out an electrician.

      Also, I wouldn't trust the people writing the codes, setting the standards, to do the wiring either. Just because they can set some engineering standards (some general knowledge + margin for error, and add some industry knowledge), doesn't mean they're qualified to wire up your home. That's kind of like asking an aerospace engineer to machine a part he/she spec'd.

    11. Re:Hell no. by Austerity+Empowers · · Score: 4, Insightful

      Well the point is as a EE I can learn real fast. I know how it works in principle, I know how to read well and understand the intent behind the rules. I could pick it up fast if it were profitable to do so. An organization that requires X years of apprenticeship in order to practice the trade would piss me off.

      On the other hand, as an EE I have no job security. My job is offshorable, and goes that way often. The reason we don't unionize is the same: it won't help. Go ahead, build "BS EE" into the law, see how many companies stop being "R&D" companies and turn to "Manufacturing" or "IP" companies. The same logic applies to IT, all that will be left are on-site help desk techs, and networking contractors (unglorified electricians: you won't even have safety on your side). All the fun server room stuff will go far, far away. That's what the ABA and AMA have that IT, and EE/CS types will never have.

      If IT wants to unionize, forget traditional labor unions. Lobby. Make the economy and tech labor issues move to the top of the campaigns. Spread your propaganda to all your union employees and astroturf the hell out of it. MADD and AARP are far more effective "unions" than the teamsters. Bend the laws to make it unprofitable to offshore. Spread beyond IT, many of us EE/CS/ME types feel the same pain you do. I'd pay dues for an organization that had real power in Washington for issues I care about.

    12. Re:Hell no. by bjourne · · Score: 5, Insightful
      I'm a union member and a software developer in Sweden. Roughly 50-70% of my collegaues are unionized. My experiences differ from yours:

      the inertia and sloppy work that comes with systems where "seniority" is more important than "ability"

      I have never experienced that. Experience is important yes, but it is not the union that decides who gets promoted. It is the boss that does that whether he is stupid or smart, because he has the money.

      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

      There are at least half a dozen professional associations for engineers in the US. Please provide one (1) example of when an engineering association has prevented someone from practicing their trade.

      Do you really want a bunch of senior people telling you what qualifications you need to have?

      My union has never told me what qualifications I need to have.

      Make American IT more expensive and less efficient than everywhere else in the world

      And American IT can't be more expensive and less efficient than everywhere else in the world because:

      1. American workers are less educated than others.
      2. American companies are very hierarchial, making adaptations to new circumstances slow.
      3. Patents and gigantic auxilliary legal costs.
      4. Poor IT infrastructure.
      5. The fact that driving people to work 60h/week with no sick leave and minimal vacations is worse for efficiency than having your staff working regular 40h/week schedules.
      ???

    13. Re:Hell no. by Moryath · · Score: 4, Insightful

      I've done helpwork for a friend, wiring up a garage-to-room conversion. We did the gruntwork, his father-in-law (who is a certified master electrician but has physical issues with getting into some of the cramped attic spacing any more due to age) taught us and inspected the work so that it could be signed off in case the house is sold later.

      I also have an EE degree. The theoreticals of the circuitry, I knew. The details of code and the reasons for how certain things are done (spacing of outlets, location and recommended height of boxes, and the biggie, NEVER try to put an electrical line through a corner, for instance) I didn't know.

      In the house I currently live in, were there to be a lot of work done, there's a certain amount of wiring that would have to be ripped out of the house because it met 1980s code but doesn't meet today's updated code. This has been confirmed by two inspectors (one when the house was purchased, one after a rebuild when my bitch of a neighbor burned her house down to scam a free remodeling out of her insurance company and damaged mine in the process).

      You may claim you can do it on your own design "perfectly safe", and building codes do differ from region to region. Maybe one area is more cautious than another. Maybe one area has different risks in terms of weather patterns (wind, humidity, etc) or has seen historical common construction flaws (soil notorious for shifting, local building materials that weren't as sturdy as another region's) that mandate some extra safety precautions.

      The point is, you can bitch all you want about "unnecessary" building and electrical codes, but you don't know everything that goes into their existence, and you should still follow them for legal reasons (and if you want to eventually sell your house, or your kids/wife might after they inherit it, etc...) even if you think they're garbage.

    14. Re:Hell no. by Jim_Maryland · · Score: 4, Insightful

      "and I must acknowledge the mysterious devaluing of IT skills since ~2001 (Microsoft's marketing for Active Directory is partially to blame: "use AD, no need for FT IT!"). It sickens me to see jobs that in 2001 paid 65K that are now advertised as $12/hr part-time (and CS degree required, WTF!!)."

      As technology advances, positions become easier. Look at the fact that in a big company you can centralize numerous servers to a single datacenter. Would you complain that this advancement caused a decrease in the number of system administrators or would you look at this as progression in the field? Should we look at the fact that system administrators no longer have to use "useradd" at a shell prompt but can use GUIs on UNIX systems and can now be administered with less skill as a reason to unionize to keep the administrators making the same pay? As a position becomes easier to fill, pay rates go down since the pool of available skilled candidates grows. Unless the position is so undesirable (septic tank cleaner probably isn't a "hot" position people are looking to work in), progression will cause it to be easier to fill.

      "Why should skilled IT pull the same pay a non-skilled day laborer makes?"

      Are non-skilled positions artificially kept to a level because of minimum wage laws? While I enjoy my salary, I certainly don't expect it to be artificially high. I'll continue to work hard and develop new skills to make sure I stand out compared to the majority of the field.

      Oh, do you consider the work of a farm laborer to be any less work than that of an IT employee? Is physical labor any less than IT labor or does IT just pay better because it generally requires a skill that many people don't learn?

      I am reminded of a comic that a co-worker had hanging in their office years ago..."Innovate or Die", with a dinosaur in the picture.

    15. Re:Hell no. by 0100010001010011 · · Score: 4, Insightful

      I deal with this shit every day. "Oh that's not my job. Get the pipe fitter." I deal with test cells running engines. Mechanics can't touch pipe fitters stuff and vice versa. Test cell operators can't touch anything. As an engineer I can't touch a single thing either.

      This is how a Unionized IT would go:
      You start your first day at your new job. You call to get a computer.
      "Sorry, I can't actually deliver your computer. We need the IT movers to move it to your desk."
      It's moved to your desk. But you, nor the movers can't plug it in (see parent). So you wait 30 more minutes for the Plugger Inner Union. (It was lunch, by the clock 11:30-12:00, no exceptions.)

      So you have your fancy new computer. You turn it on. You need Office. Sorry, but the Office Installer Union is actually backed up. The Matlab Installer Union could do it, but they're not "officially trained" nor do they have the certification.

      You wait another day to get Office... you're up and running. Then your NIC craps out. You call the help desk union and they send the NIC repair union. NIC repair union says that it's a software problem. Windows XP Software union rep says it's hardware.

      Cycle repeats for 2 days. You say "fuck it". So you fix it yourself. A NIC rep sees you do this and writes a grievance against you. He now gets paid to do the install even though he did nothing. Your boss bitches at you not to touch anything because too many grievances and you're in trouble.

    16. Re:Hell no. by hairyfeet · · Score: 4, Insightful

      As a self taught guy who has been building,repairing,and networking PCs since the days of DOS 3, I say it would be a bad idea. How in the hell would you even figure out what to label a guy like me? I have built networks,configured SMB rollouts,custom designed PCs based on performance,power usage,size,etc, worked on embedded medical units, worked up security plans,etc and etc. But if you look simply at the paper all I have is an associates tech degree.

      But one thing I learned a LONG time ago was the difference between a "paper tiger" and a guy that actually knew his stuff. And often the guys I find that really know what they are doing DON'T have any degrees at all,they just love the work and have been doing it since they could get their hands on their first machine. Hell,the best damned website builder I ever saw was a 16 year old girl who could build wonderful rock solid business websites using nothing but an old 400MHz laptop and freakin' notepad!

      And while I would LOVE to have a united voice against stuff like the flood of H1-Bs,the simple fact is it will end up just another hoop we have to jump through and another corrupt organization. If we want a united voice we should build something grassroots like the EFF for IT guys. Some place we can volunteer time and money to to give us a lobbying group,since that seems to be the only thing our bribe takers...oops,mean faithful congressmen and women seem to listen to these days. But the LAST thing we need is another BS group giving us more hoops to jump through. Because degree or not,if I need a business website done I'm hiring the 16 year old girl,thank you very much. Because unlike many "web designers" I have met she knows her stuff. But as always this is my 02c,YMMV

      --
      ACs don't waste your time replying, your posts are never seen by me.
  2. Should IT unionize? by qoncept · · Score: 4, Insightful

    This article answers it's own question. "... all for a job that could be outsourced tomorrow." What better way to ensure you don't have a job than to make yourself more expensive than a contractor?

    --
    Whale
  3. Re:Fine by me but... by SatanicPuppy · · Score: 4, Insightful

    If you unionize, your employer has far less rights regarding workmanship and professionalism than if he can simply fire someone who displays neither. He also has fewer options come hiring time.

    By all means, lets restrict all IT work to people who have the piece of paper, rather than the actual ability. In my experience the people who want the former, are the people who lack the latter.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  4. The main problem with a professional organization by Omnifarious · · Score: 4, Insightful

    Is that one of its first tasks will be to lobby for a law requiring that membership in it become mandatory for anybody practicing in the field. No thank you.

    Unions are broken for very similar reasons. Basically, any large organization that claims to 'represent' you actually represents itself and only has your interests as a peripheral matter because appearing to cater to them is how it gets political power.

  5. Sixty-hour work weeks with no overtime... by AKAImBatman · · Score: 5, Insightful

    ...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.

  6. One racket too many. by Lilith's+Heart-shape · · Score: 4, Insightful

    Isn't this really what is comes to? You're just paying money out of your check for someone else to tell you what to do.

    I already give money to one protection racket: the government. Why should I give money to another, run eventually by the mafia?

  7. Hell yes. by SilentChris · · Score: 5, Insightful

    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.

    1. Re:Hell yes. by aggieben · · Score: 5, Insightful

      Unionizing doesn't even make sense. The IT industry is the one industry more than any other where market forces really are at work: you don't like your job? Go get another. There's a bajillion IT jobs across a bunch of different industries, and IT workers are very, very mobile. You don't need a union, because the active market already protects you from bad management. We haven't f****d anything up. Quit your bitching and get another job.

      --
      Don't become a regular here, you will become retarded. -- Yoda the Retard
    2. Re:Hell yes. by Pope · · Score: 4, Insightful

      What did we do to our industry?

      Setting unrealistic expectations to the management/managers by trying to be lone superheroes all the time.
      Poor, unclear, late or non-existant communication.

      Hell, I'm guilty of it myself from time to time. But I know the problem and I'm trying to fix it.

      --
      It doesn't mean much now, it's built for the future.
  8. Re:You Have 2 Choices... by JBMcB · · Score: 4, Insightful

    Let me fix that -

    1) Unionize and loose your job to outsourcing or contractors in a few years

    2) Continue to be abused, until you work with your employer to fix the situation, or quit and go work somewhere else

    --
    My Other Computer Is A Data General Nova III.
  9. Re:Fine by me but... by Ostracus · · Score: 4, Insightful

    "By all means, lets restrict all IT work to people who have the piece of paper, rather than the actual ability. In my experience the people who want the former, are the people who lack the latter."

    So what are you saying? That people with the ability couldn't get the piece of paper?

    --
    Shai Schticks:"You don't make peace with friends, you make peace with enemies"
  10. Of course not by goose-incarnated · · Score: 4, Insightful

    All those posting here believe that they are of above average quality and that their job is not going to go away merely because they are so damn important. The only people who would lose their jobs are those incompetent anyway.

    The fact that they have no bargaining power or that their skills are irrelevant when it comes to cutbacks ... just too inconvenient to consider ... so no unions or trade association. Only *losers* would need those things after all

    --
    I'm a minority race. Save your vitriol for white people.
  11. Sweet Zombie Christ, No by StealthyRoid · · Score: 5, Insightful

    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.

  12. Re:Huh? by SatanicPuppy · · Score: 4, Insightful

    Ignorant you may be, but you hit the nail on the head.

    Unions don't make any industry more efficient, and that loss of efficiency can mean the difference between a successful company and an unsuccessful company. If the work can be done more efficiently by non-union employees, it will be, and IT work is very portable...You can't do the old Union trick of changing the laws in a geographic area when someone across the world could be doing your job remotely.

    It comes down to market issues. If you're top notch at what you do, and there is demand for that skill, you'll have work. If your skills are dated, if you're not qualified, you could have problems. Lot of people jumped into the industry in the 90's with extremely limited skillsets. If you can't roll with the changes, you're going to get pushed out.

    The industry is really volatile right now, and that makes people crave the sort of stability that Unions seem to provide, but there is a difference between stability and stagnation.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  13. Yes, tech workers need unions by nysus · · Score: 4, Insightful

    Yes. It is the corporate DNA to pay workers as little as the can get away with and produce as much work from workers as possible. That's just the nature of capitalism. By joining a union, workers can push back against being treated as nothing more than a disposable tool.

    Are unions perfect? Of course not. But neither is anything institution run by mortals. But like anything, you have to weigh all the advantages and disadvantages.

    There's no question unions have brought more balance to laissez faire capitalism. Unfortunately, they have become victims of their own success. Health care, vacation pay, pensions, 40 hour work weeks, overttime, health and safet regs, etc. All of these were the result of workers pooling their money and getting themselves political muscle. Believe me, it wasn't given to them. Ask you grandfather or great grandfather who got his head cracked open with a club for participating in a strike.

    Unfortunately, it's in most people's nature to be sheep and be complacent to try to protect what they have. Why risk your job by going against the company's wishes to remain union free. It won't be until workers really feel the sting of boots on their necks grinding them into the pavement will workers actually get pissed off enough to fight back.

    So, look for your hours to get even longer, your paychecks to shrink even more, and lose more benefits before unions can become a reality.

    But ff they were smart, and could learn to stick together (get over that rugged individualism bullshit they like to believe), techs could do a lot for themselves here and now.

    I should know. I'm a union guy working in the tech industry.

    --

    ---Technology will liberate us if it doesn't enslave us first.

  14. Re:no by Count+Fenring · · Score: 4, Insightful

    Also, let's not forget that Unions helped bring about the 40 hour workweek, overtime, and other such. They help even non-members when they have enough push to get labor-friendly legislation passed.

    And yes, unions exert pressure (or harm, if you prefer) on businesses WHEN THEY'RE ON STRIKE. That's the effing point. Striking is a response to management harming the workers through failing to provide a decent work environment. If a business is "hurt" by a demand for a living wage, well, it deserves the pain.

    Certainly it's possible to go overboard the other way, and destroy the ability of businesses to function... in theory. In PRACTICE, right now, businesses have more rights and power than the citizenry, and it's catastrophically not good.

  15. Speak for yourself by reidconti · · Score: 4, Insightful

    No. I like working longer hours some days and spending the odd afternoon at the pool. I like having a non-adversarial relationship with management and playing foosball with my boss. I like being free to negotiate my OWN salary. I like participating in an industry where free thought reigns, not a mob mentality.

    It's the union members who are sheep and do whatever the union tells them to do.

  16. Unions will really backfire on the IT indrustry. by jellomizer · · Score: 5, Insightful

    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.
  17. Re:Protected from Competition by TaoPhoenix · · Score: 4, Insightful

    Bingo.

    One reason we moan about lawyers is the artificially protected fees. For simple filings the level of knowledge "should cost" some $50 an hour tops, and small cases could escape under a grand.

    Then Orgs. like the RIAA reverse-leverage this fact to pull their copyright stunts.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  18. Re:unionization = siren song by catmistake · · Score: 4, Insightful

    I consider myself an IT professional, and I got my degree in Japanese Literature.

    Awesome. I too consider myself an IT professional, and have a degree in Philosophy. I thought this was rare until last week... had interviews for 2 seperate positions where I met 2 Philosophy grads working in IT. I, for one, think Computer Science grads should stick to the Science (or development or the CIO, CTO, or Chief Archetecture slots) and leave the 'practice' of computers to the experts. They are devaluing their expensive education and helping to drive our salaries down. Do lawyers work as paralegals? Do sugeons take jobs as nurses? Get out of my field, you stupid geniuses!