Ask Slashdot: What Would It Take For Developers To Start Their Own Union?
juicegg writes "TechCrunch contributor Klint Finley writes that developers have shunned unions because traditional workplace demands like higher pay are not important to us while traditional unions are incapable of advocating for what developers care about most while at work: autonomy and self-management. Is this how most developers feel? What about overtime, benefits, conditions for contractors and outsourcing concerns? Are there any issues big enough to get developers and techies to make collective demands or is it not worth the risk? Do existing unions offer advantages or is it better to start from scratch?"
In my lifetime, I don't recall a single industry that that has started a successful union in the U.S. (not in ANY field). All the unions that still have any real power are the ones still around from the Roosevelt New Deal and postwar days (the Teamsters, UAW, etc.).
So it's hardly fair to single out developers. There are very few fields that are significantly unionized anymore, and most of the ones that are are represented by older unions that go way back. When you look around and see that there are no unions with any real power that have been founded in your lifetime, it's pretty easy to be skeptical and pretty hard to volunteer to be the sacrificial lamb (by being the first voice in your field supporting a union) and endanger your career in the process.
It probably also doesn't help that political support for unions, even among many Democrats, pretty much dried up a long time ago.
What political party do you join when you don't like Bible-thumpers *or* hippies?
"because traditional workplace demands like higher pay are not important to us"
Since when is higher pay simply "not important"?
TK
The second a union starts, the company closes the local shop and outsources all development to a place where unions are illegal.
Manufacturers at least have a direct cost associated with moving a factory; most costs attributed to outsourcing are intangible in development and are thus usually ignored by PHBs.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
Before the Internet, and before the common man had access to rally others, communicate to the masses, and see others' opinions, unions had value.
They kept child labor in the mines but made more money for the children's parents and for the union bosses.
Today unions are obsolete. The only people who advocate unions are the unions themselves, and those who've already joined that now want to "haze" everyone else because "they got hazed."
Sorry, jack. No unions.
E
Why would you want a Union? My observation is that Unions drag everything to the mediocre. It drags down the top performers and brings up the dead wood. If i'm a top performer I can do better for myself on my own. I guess if I'm a bottom feeder I'm interested, but probably too lazy to to care.
It would be a hard sell to the development community these days. Especially when we're facing overseas competition, and domestic competition from overseas labor. A union would make American developers un-competitive, and force businesses over the edge of insisting they can't afford american labor, even further. Sure, it would be nice if congress fixed that, but they haven't in the twelve years I've been watching. So, it's probably not feasible any time soon.
This signature intentionally left blank.
while traditional unions are incapable of advocating for what developers care about most while at work: autonomy and self-management
They missed one other one: Unions are also incapable of supporting performance-based rewards and promotion, something tech sector workers appreciate. The notion that seniority trumps all else would not go over well in my workplace, nor former workplaces.
I know programmers who work for my county that are unionized. Imagine a process where seniority and not coding ability determines who works on a project.
Imagine a union that helped get the best workers on a project and making the most. A union that helped weed out the lazy, the incompetent, and the criminals. That would be a union that most people would not oppose.. unfortunately the opposite is true: seniority rules, criminals are coddled, lawsuits are filed, work slowdowns are part of the union bag of tricks.
Unions have no place for the programming industry.. except in government where we expect cost overruns and shoddy results. To start a programming union would be to hasten the outsourcing of your job. Besides, programming jobs are one of the most in-demand careers out there. If you can't make good money without a union, you should bone up on your skills.
In C, it's pretty simple, though of course if you want a discriminated union you'll probably end up stuffing it into a struct along with a field that tells you how to interpret the union.
Today, unions exist to protect jobs - meaning that a poorly performing worker is protected and cannot be fired.
Technical people admire knowledge, ability and competence above anything else. And they are disgusted by incompetence, which makes everybody's work more difficult.
The idea of actually protecting incompetence (via unions) goes against the whole technical culture. No, unions are not coming to the development community.
I haven't heard of any either, but I could clearly see a white collar information technology union. The need for one is quite apparent.
Odd, I have not seen a need to have my paycheck garnished in order to pay the wages of a bunch of executives who do nothing for me. You already get enough of that with company management as it is.
As financial conditions deteriorate, and simultaneously the need for more IT labor increases, the more management is pressured to "get more for less."
As the need for IT labor increases so does the amount you can ask to be paid, and the greater the opportunity to switch jobs for higher pay.
Eventually there has to be a breaking point.
We reached it a while ago. Unions are broken, and developers are way too rational to bring long term harm on themselves for short term gain.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Unions exist in situations where management is negotiating from a place of power and replacement workers are easy to find. They allow the collective workforce to get a better deal than they would individually.
Meanwhile, there is a shortage of capable developers and we have the power in most negotiations. Why do we need a union if we can just demand what we want and get it? In our industry, companies have even been caught uniting against workers.
Unions are a tool and developers are taught to us the right tool for the job. When the situation demands a union, we'll unionize, but there's no point in doing that until there are a ton more capable developers to compete with for jobs.
"Don't blame me, I voted for Kodos!"
Communism may have failed, but class warfare is alive and well. A worldwide depression, or even that of a few nations like the USA, India China or Europe would probably kick start a move to unions. I have no doubt that even if wages were to drop to Bangladesh levels, that prices on most items in these countries wouldn't budge downward very much. Price structure and wage structure are increasingly out of sync. At a certain point, when nobody in IT is making enough to live on, unionization will occur, along with a the sharpening of some makerbot printed guillotines. The speed with which "libertarians" become socialists will be quite amusing.
Please do not read this sig. Thank you.
Disclaimer: I'm live and work in Europe
...where you already have 4+ weeks vacation, sane working hours, protection from dismissal without cause, guaranteed health care if you do lose your job, and so on and so forth. Understandable that you don't see the appeal of a better contract.
0 1 - just my two bits
The OTHER big problem with white collar workers is that your job performance and satisfaction are far more likely to be influenced by the performance of your coworkers.
If a guy on the factory floor is slacking, the company's production goes down.
If a guy on your software team is slacking, it can quickly become a pain in your ass.
A tech union would just open the door for workers who can't perform to vote themselves protections that limit the compensation and satisfaction of the workers who do perform well.
paintball
While everyone would love to run their own business, there are profound inefficiencies associated with having a large numbers of small businesses, mainly losses caused by competition and misallocations of labor. Having a large proportion of small businesses is actually a symptom of a backward or developing economy; Egypt has more self-employed per capita than the US, for example.
Don't blame me, I voted for Baltar.
We're talking about programmers, aren't we? Very few programmers "deal retail", e.g. writing a Java applet for Mrs Scroggins down the road. They generally work for medium to big companies.
Thus I don't see how you've addressed any of starworks5's concerns.
I can be as self-employed & personally-incorporated as I like, but that's going to make zero difference if Sanjeet in Bongobongoland will work all week for less than the cost of my morning coffee.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Most industrialized nations can manage to provide healthcare of very similar quality to what insured Americans enjoy to their entire populace, and the total bill comes in at ~40% less than what Americans pay. Under single-payer, it is entirely plausible your bills will go *down* (and I can prove that possibility with more than a dozen real world examples).
I hold that America does not need to be uniquely incompetent at providing affordable healthcare forever.
http://www.forbes.com/sites/frederickallen/2011/12/21/germany-builds-twice-as-many-cars-as-the-u-s-while-paying-its-auto-workers-twice-as-much/
Frederick E. Allen
12/21/2011 @ 5:42PM |60,178 views
How Germany Builds Twice as Many Cars as the U.S. While Paying Its Workers Twice as Much
In 2010, Germany produced more than 5.5 million automobiles; the U.S produced 2.7 million. At the same time, the average auto worker in Germany made $67.14 per hour in salary in benefits; the average one in the U.S. made $33.77 per hour. Yet Germany’s big three car companies—BMW, Daimler (Mercedes-Benz), and Volkswagen—are very profitable.
How can that be? The question is explored in a new article from Remapping Debate, a public policy e-journal. Its author, Kevin C. Brown, writes that “the salient difference is that, in Germany, the automakers operate within an environment that precludes a race to the bottom; in the U.S., they operate within an environment that encourages such a race.”
There are “two overlapping sets of institutions” in Germany that guarantee high wages and good working conditions for autoworkers. The first is IG Metall, the country’s equivalent of the United Automobile Workers. Virtually all Germany’s car workers are members, and though they have the right to strike, they “hardly use it, because there is an elaborate system of conflict resolution that regularly is used to come to some sort of compromise that is acceptable to all parties,” according to Horst Mund, an IG Metall executive. The second institution is the German constitution, which allows for “works councils” in every factory, where management and employees work together on matters like shop floor conditions and work life. Mund says this guarantees cooperation, “where you don’t always wear your management pin or your union pin.”
Mund points out that this goes
against all mainstream wisdom of the neo-liberals. We have strong unions, we have strong social security systems, we have high wages. So, if I believed what the neo-liberals are arguing, we would have to be bankrupt, but apparently this is not the case. Despite high wages . . . despite our possibility to influence companies, the economy is working well in Germany.
At Volkswagen’s Chattanooga plant, the nonunionized new employees get $14.50 an hour, which rises to $19.50 after three years.
http://www.remappingdebate.org/article/tale-two-systems
A tale of two systems
By Kevin C. Brown
Remapping Debate
Dec. 21, 2011
American autoworkers are constantly told that high-wage work is an unsustainable relic in the face of a hyper-competitive, globalized marketplace. Apostles of neo-liberal economic theory — both in the public and private sectors — have stressed the message that worker adaptation is necessary to survive....
But the case of German automakers — BMW, Daimler, and Volkswagen — tells a different story. Each company produces vehicles not only in Germany, but also in “transplant” factories in the U.S. The former are characterized by high wages and high union membership; the U.S. plants pay lower wages and are located in so-called “right-to-work” (anti-union) states.