- Pay is based on seniority, not skill
- You have to please your boss from the company and also the union
I don't want either of these things. If there is a union where this doesn't happen then I could consider it.
Lets call it a professional organization instead, and I think what most of us want is collaborative bargaining around IP(companies doesn't own your off hours) and non-competes.
Think Tom Cruise is paid based on seniority and not skill?
After all, why would tech workers choose that pay scale when putting together the rules for their union?
(And, if they did choose that, whose place is it for anyone outside the union to tell them that's wrong?)
travis stated pay is based on seniority (implied most, not all). You claimed his sample was too small, then gave a small sample as counter-evidence. So now that I ask you if the majority of people in unions are paid based mostly on seniority you admit you don't even know? And thus claim it's irrelevant?
That's an odd way to demonstrate that your objection has merit.
You can look up the biggest unions in the US, and you will in fact see that a significant component of pay is seniority based for the majority of people in US unions.
If you're going to complain that someone is wrong, at least put in some legwork.
If tech workers unionize, they can decide whatever pay scale they want. Why do you think that is not so?
And if they choose a pay scale based on seniority, lines of code delivered, or the weather, what difference does it make to you, someone presumably not a member of their union?
A software eng that cant see this prob/solution most likely isn’t a good software eng and would benefit from said union.
I was a full-time employee of an enterprise software consulting company my first job out of college. We were paid salary and didn't get overtime. We did get comp time, but only for hours worked in excess of 95 every two-week paycheck (so you'd have to work 7.5 unpaid overtime hours per week until you started getting comp time). I also had several managers who wanted us to bill the contractual maximum of 40 hours per week for clients, which in practice meant that I worked a lot more than 40 hours per week once travel and various administrative tasks were factored in.
I burned out at that job in less than four years and left to do something else that didn't involve so much time spent away from home at godforsaken little cities.
Hollywood actors and other people in showbiz? Professional athletes? Doctors?*
*https://www.forbes.com/sites/johngoodman/2014/09/03/the-doct...
What amazes me is, for how curious tech workers tend to be about, say, new frameworks or languages or whatever, they're so amazingly incurious when it comes to talk of unions--and in fact not just incurious, but so willing to repeat stuff that just isn't true.
Are you just making up SAG claims throughout this page? Did you look to see what SAG members actually make?
Avg SAG member makes far less than a software developer. Tech superstars make well over an order of magnitude more than an avg SAG member. Tech superstars include unicorn founders, who again make more than an order of magnitude more than even the very top stars.
Here's one place listing how low SAG members generally are paid. You can find others if you like.
https://www.backstage.com/news/actors-income-falls-far-below...
Also, yeah, a handful of tech company owners make more than actors? So? Does that matter at all to the rank and file, who, by fault of not acting collectively, are leaving money on the table year after year? "Your boss is a billionaire, don't unionize" is the argument to make here?
From the numbers I posted, the majority of tech workers make far more than the majority of actors. Do you dispute this?
If the benefits of unions were so clear, would you have to keep using this comparison dishonestly?
Never.
> Ask yourself how many times a colleague on a visa told you they felt trapped.
Never.
> Ask yourself how many times you’ve heard of a colleague get fucked out of their vacation due to a critical issue.
Never.
> Ask yourself how much power you have to effect change when it comes to just general process
Hmm, somewhat. All places I've worked have been pretty responsive. Current place moreso.
I suggest the above is USA-specific and nothing to do with unionised programmers.
I don't think we need collective bargaining on salaries. But I do think workers should have a unified voice at the table, and at the very least have a political lobby for their rights.
There are a lot of lower level tech employees in modern tech companies that don't have the luxuries or benefits software engineers do and get stomped on all the time. It's really only engineers who have 'cream of the crop' jobs and benefits.
Speaking from a software engineers perspective, the need for unionization is pointless. Software engineers are at the top or near the top for most jobs in terms of compensation - so the need for unionization isn't as necessary.
My tech coworkers live in the dingiest of apartments. Housing prices are outpacing gains in salary, and the majority of housing is out of reach of the median tech-worker salary.
There are some exceptional positions at exceptional companies, such as FAANG, but I strongly believe they're exceptional. Frankly when I look around my office I see either a bunch of young engineers working too long and too hard for a salary that won't really ever get them anywhere, or folks who already got their share of the pie. (And perhaps are quite fine on a SV salary.)
I'm also strongly considering leaving the Bay Area, as I'm tired of trying to change the minds of a generation that doesn't want me here.
I do executive tech support & linux support for corporate and live in a 1br apartment from the 60's 10 miles outside of the city. My commute is 1-1.5hr every day on the bus. I can't afford to use my health insurance even though I pay the premium every month.
It's absolutely true that costs are outpacing salaries, and a majority of them aren't "cream of the crop".
Perhaps I should've been clearer in my comment. If we're including call centers and first level support in "tech workers" then that changes things, just like including laborers in a steel mill as "steelworkers" would change things. Strictly from a software development/engineer perspective, unionization makes little sense right now.
If we're including low skill tech workers, then sure, their benefits won't compare. I was looking at it from a different PoV.
A union is a mechanism for individuals to pool labor and achieve greater return from that labor than any of them would using only their own personal resources.
The only difference between them is the resource being pooled. As a result, I have great difficulty understanding why people are accepting of one but condemn the other.
If you want to compare unions to corporations, consider this: What if all the local companies got together and agreed to only pay tech workers minimum wage? By pooling their bargaining power, they can achieve a far better result!
This is of course illegal (at least I'm pretty sure it is), but even if it weren't, it would be easy for startups to take advantage of: Suddenly, there's a surplus of tech workers looking hard for different work. Unions have the same problem: Some people might be happy to work for wages that the union considers unfair, causing the union to collapse. Unless, that is, there were some law requiring the businesses to only hire from the unions.
I'm extremely happy to be employed in a field where I have natural bargaining power that doesn't need to be augmented by legislation. The day programmers unionize is a sad day indeed: It's just a few years before the whole profession is automated or outsourced away.
What if all the local companies got together and agreed to only pay tech workers minimum wage?
Rather than use a hypothetical, lets use a couple of actual things that have happened; "all the local tech companies got together and:"
* agreed not to offer jobs to the other's workers
* agreed to get H1B visas rather than pay hire wages
* converted previous employee jobs into contracting
These are all things that have happened which could not be counter acted by disorganized labor pools. So when you say "I'm extremely happy to be employed in a field where I have natural bargaining power that doesn't need to be augmented by legislation." I expect you will find at some point in your career that your "natural bargaining power" will erode and you will be in a position where the lack of any bargaining power will benefit the corporation disproportionately.I think it is great that this hasn't happened to you yet but it would be unwise to assume it will never happen.
And this would be totally fine if we valued corporate rights over individual rights.
But as a society, we value individual rights over corporate rights, which is why we allow for unions but not corporate collusion. Any individual cannot stand up to a corporation, but a union of individuals certainly can, supporting the subjective values of our society.
Unions are corporations. They are corporations which claim to represent their members' interests, but under US law, they are not obligated to. (And fittingly, there is actually plenty of evidence to suggest that many do not, which is one of the reasons for decline in both overall union membership and the decline in support for unions among union members).
I wonder how it came to be illegal. Did legislative bodies pass laws to protect workers solely out of the pure and spontaneous goodness of the legislators' hearts?
Or did they pass these laws because people organized and agitated and worked to get these laws passed?
If only there were some sort of books of history we could go look this stuff up in to find out.
And I think you'll find corporations have problems and excesses, too, but you seem perfectly willing to tolerate those.
As to the rest, see the other replies: "I have and have always had good bargaining power" does not imply "I will always have good bargaining power". In fact, the belief that how things are now is how they always must be is one of the most basic economic mistakes a person can make.
Wait, are you really going to try and give unions credit for antitrust laws (ie, the laws that OP is referring to)?
The first antitrust laws outlawed collusion, which also had the effect of outlawing a lot of common union activities as well. Labor unions fought to exempt themselves from antitrust laws.
Nobody's saying that these were "utterly independent forces". I'm pointing out that the relationship between them was the exact opposite of what you claimed. Labor unions opposed antitrust laws which outlawed the sorts of behavior OP described; they certainly weren't responsible for it like you tried to claim.
It sounds like you're interested in ignoring the actual details of the history which disprove your point, in order to paint a certain narrative. In that case, there's probably not much point in discussing further, because that's not what a good-faith discussion looks like.
But I didn't imply that. What I said was that it makes me happy to be in that position. Requirements may change in the future, but I am capable of change as well. Rather than invest in a union to protect me as I become obsolete, I'll invest in my own development to do my best to ensure that doesn't happen.
Programmers are hired without unions for a reason, not because nobody's thought of it yet. Unions are a last-resort crutch to prop up unsustainable employee-employer relationships. Nobody should want to transition from being beholden to no-one to owing their employment to both a union and a government. I could scarcely live with myself.
That is flat out not true.