[matthewmacleod]

I think you can just look at the surface and see it as a natural consequence of a relatively easy, high-income, unregulated profession, with high demand for workers. Many of the benefits of collective bargaining aren't applicable to people who are relatively easily able to switch jobs or work as a consultant. That then tends to lead to… complacency, I guess? I would expect that relatively few people in that field have recently been in a situation where collective bargaining would have been a benefit to them, and that allows them to see only the downsides.

I do notice some agitation in the direction of unionisation from some parts of the industry – particularly in game development, where conditions can often be worse.

[SolaceQuantum]

I can think of a mountain of things that programmers could collectively bargain for that would benefit everyone. I'd like for bargaining to happen about parental leave, what "unlimited vacation" actually means, what "on-call" duties really entail, compensation for overtime, and whether or not engineers can be reasonably forced to perform illegal or unethical behavior (data collection, dark pattern designs).

[vips7L]

You are not forced to do any of those things. You are able to find a new employer whenever you want.

[SolaceQuantum]

I might not able to find a new employer whenever I want. I might not have time to job search because I have children. I might have dependents or I myself need critical medical care that cannot be interrupted by job hopping. I might have a family emergency that has destroyed my savings to look for a new job. I might be in the point of my career in which leaving for a new job so soon would be a red flag to employers. I might have just made a large purchase (a home, for example) that means I cannot afford to find a new employer at the exact moment my current asks me to be on-call for the next 72 hours nonstop.

And if it's not me, it might be my co worker, who I know is a new parent and cannot afford to stop working to care for their child. It might by my mentor, who is dealing with ageism making it difficult to find work. It might be my mentee, who is being discriminated against because of their H1B status. It might be my new hire, who accepted a lowball offer because they have no knowledge of price transparency. It might be a software developer I just met at a data science meetup, who is being worked to the bone at a startup but doesn't have enough experience to be hired anywhere else.

Life is not so easy. We're all struggling. We should be working to back each other up so that individual people are not being exploited and then have to fight by themselves against an entire corporation.

[techsupporter]

> Life is not so easy. We're all struggling. We should be working to back each other up so that individual people are not being exploited and then have to fight by themselves against an entire corporation.

Exactly this.

This is why I work the requested 40ish* hours per week that my employer purchases in bulk from me, and rarely more. It's not because I'm lazy or unmotivated. I work very hard while I am working and I do more than the baseline my employer requests of me. My management thinks highly of me and I am well-compensated for my efforts, so clearly my employer values the contributions I make.

I do the work hours I do and how I do them, pushing back on unreasonable on-calls and repeatedly staying late, because I am senior so I have the voice to be able to discourage management not staffing our group appropriately and not setting unreasonable deadlines. I make sure my juniors know, too, that the way to your personal success is a healthy work-life balance that works both for you and for the group of people in which we are ensconced. I also make sure I mentor my juniors and I do what I can to help others be more efficient and effective.

No one should have to burn the candle at both ends just to be able to be seen as doing a good job.

* There are exceptions, of course. I am not inflexible, because that's unreasonable, but my employer pays for approximately 40 hours per week of my valuable single life in this universe and 40 hours, roughly, is what it shall receive.

[techntoke]

Agreed.. thank you for being aware of these issues. I find the tech industry to be pretty toxic & corrupt overall, usually rewarding the employees that are the least ethical.

[hoaw]

Not if you want to actually have a career. This isn't day labor. To be successful in the industry you have to be part of good projects. Those often require at least a couple of years investment. And that is in addition to building a life outside of work.

[fixermark]

Although vips7L is getting downvoted into the gutter, their response is exactly the attitude I observe permeating Silicon Valley that can help explain the lack of interest in collective bargaining.

[rconti]

This. And due to the high demand of our skills, we're able to effectively negotiate salaries and comp in a way that at least lets us think we're doing better than average (see: salary transparency, or lack thereof).

Plus, we're not a group generally known to like more layers of bureaucracy.

[jancsika]

> And due to the high demand of our skills, we're able to effectively negotiate salaries and comp in a way that at least lets us think we're doing better than average (see: salary transparency, or lack thereof).

So even with a history of Silicon Valley playing tricks to suppress what developers get paid[1], the typical HN reader is humdrum about salary because it's "better than average?" I have a hard time believing that.

> Plus, we're not a group generally known to like more layers of bureaucracy.

I get that.

But doesn't this seem weird:

1. Devs apparently don't care for the bureaucracy of the taxi medallion service. So two companies build a nationwide service that does an end run around it.

2. Devs apparently don't care for the lack of salary transparency. So they create a cryptographic system that... oh wait, nope, there's no app for that.

?

[1] https://www.telegraph.co.uk/technology/news/11843237/Apple-G...

[fixermark]

> So even with a history of Silicon Valley playing tricks to suppress what developers get paid[1], the typical HN reader is humdrum about salary because it's "better than average?" I have a hard time believing that.

Yes, because the "pay suppression's" effect was to knock people making six-figure salaries down to six-figure salaries, on average. It actually had very little observable negative effect.

(Note that if you go back to the original lawsuits, they were regarding gentlemen's agreements around headhunting. Given that SV's default attitude is "individuals are responsible for themselves," an agreement against headhunting isn't interesting---if an employee is dissatisfied, they know where the competition is and who to talk to about changing companies. If anything, there's a weak positive to an anti-headhunting agreement for employees at the companies in question: it was one fewer recruiter squads pumping spam into an employee's inbox).

[rhizome]

Note that if you go back to the original lawsuits, they were regarding gentlemen's agreements around headhunting. Given that SV's default attitude is "individuals are responsible for themselves," an agreement against headhunting isn't interesting---if an employee is dissatisfied, they know where the competition is and who to talk to about changing companies

You may be interested to learn that one of the corrupt agreements was that in the event that an employee does talk to the competition about changing companies and one of the other colluding companies makes an offer to the employee, that company will not counter-offer beyond the first offer.

So, "little observable negative effect" is not quite as dispositive (or even as visible) as you portray it would be.

[fixermark]

It's still, on average, a choice between two very cushy six-figure-plus-stock-options deals. No doubt collusion like that puts downward pressure on salaries, but with so much inequality in income in the US, you could put a LOT of such downward pressure on salaries before anyone's going to bat an eye.

(Hm... There's either an economics or sociology paper in the making there about the consequences in employment practices when the wealth inequality in a nation skews large).

[rhizome]

This is one of the most worker-hostile perspectives I've read in a long time, certainly in a dismissiveness-per-sentence sense.

[aquadrop]

You need antitrust laws to work not unions, when SV companies had secret agreement.

And for 2 - there's app for that, but I don't think the statement is generally true.

[TAForObvReasons]

It's more "temporarily embarrassed billionaires" imho. Many HN denizens are angling to either work at google or launch a startup that is acquired by google or grow to the scale of google. Why offend the future employer / acquirer now over proletarian issues?

In case you aren't familiar with the Steinbeck quote:

> Socialism never took root in America because the poor see themselves not as an exploited proletariat but as temporarily embarrassed millionaires.

[rconti]

Seems like a massive projection, but okay.

I'm not sure the pro-union crowd are doing themselves any favor by constantly telling people they don't know what they want, insisting things could only be better, inventing straw-man arguments, and so on.

[acct1771]

"Embarrassed" -> "disenfranchised" has a nice ring to it.

[novembermike]

This is misquoted quite a bit. Here's the actual quote.

"Except for the field organizers of strikes, who were pretty tough monkeys and devoted, most of the so-called Communists I met were middle-class, middle-aged people playing a game of dreams. I remember a woman in easy circumstances saying to another even more affluent: 'After the revolution even we will have more, won't we, dear?' Then there was another lover of proletarians who used to raise hell with Sunday picknickers on her property. "I guess the trouble was that we didn't have any self-admitted proletarians. Everyone was a temporarily embarrassed capitalist. Maybe the Communists so closely questioned by the investigation committees were a danger to America, but the ones I knew—at least they claimed to be Communists—couldn't have disrupted a Sunday-school picnic. Besides they were too busy fighting among themselves."

[simion314]

What is different then the acting though? Actors have unions that protect their rights but don't affect their salaries AFAIK (maybe they were abused so much that the history if fresh for them still?)

[idontpost]

The difference is that actors were treated like shit first. Even the stars. Just look at what they did to Judy Garland, not to mention everyone else on Wizard of Oz.

That hasn't happened yet to developers.

[hoaw]

> That hasn't happened yet to developers.

I know a fair number of developers who aren't doing that great, or at least not as well as they should. Life quality issues are very common. It is for instance very common to get screwed on salary, pension or vacation at some point of your career, be let go because a project was mismanaged, having a dysfunctional work environment or any number of issues were developers draw the last straw.

Edit: To add to this. I think people don't understand the "failure mode" of being unorganized. It isn't that it is going to be bad all the time. It is that since you don't have a voice other people don't have to consider you. Which means that the likelihood that you will be negatively affected by both small and large decisions of other people increases over time. And that isn't necessarily something you can correct after the fact. Getting unduly interrupted in your career, working in a bad environment or not getting credit is something seemingly small can really affect your life long term. And at least many people I know have these types of stories.

[Dangeranger]

You may want to think back just 25 years to the early to mid-nineties when developers where considered “code monkeys” who couldn’t think past their current module and needed “business analysts” to write requirements for them.

It wasn’t slavery by any stretch, but working in programming was akin to working in “IT” and thought of as a department full of weird nerds who cost the company money.

[dragonwriter]

Separate business or system analysts managing requirements documentation weren't (and aren't in the many places where they are still a thing) about developers being “code monkeys” with limited and not particularly valued skills, in fact, it was and is usual for such analysts to be considered inferiors to the programming staff who do work that is beneath programmers worth.

The reason they exist is because the organization values (or is subject to mandates for) documented requirements, and doesn't want programmers to have to bother with the tedious work of developing and maintaining them, focussing on actually developing the software.

[Dangeranger]

Thank you for your perspective.

Was this always the case though? Perhaps my position is colored by my experience working for a former IBM manager who thought of programmers as those who “just write the code” based on the requirements written by the “more senior” business analysts.

That particular experience reeked of superiority of managers, project managers, and the business analysts who worked directly for them. I admit that my experience could have been anecdotal, however I’ve asked several senior programmers who were active in the nineties who have confirmed the relationships were by and large toxic at the time.

[fixermark]

Correct, but perhaps unions didn't arise from that because the model failed---that era of Silicon Valley died in the dot-com bust.

The second generation of dot-coms that succeeded centered developers as domain experts and essential to company survival (broadly-speaking; there is certainly variance).

[rchaud]

Remember this story from not too long ago about getting rid of older workers at IBM?

https://news.ycombinator.com/item?id=16648000

Here's a choice quote:

"But, the new documents added, employees had to waive the right to take their age cases to court. Instead, they had to pursue them through private arbitration. What’s more, they had to keep them confidential and pursue them alone. They couldn’t join with other workers to make a case."

[Apocryphon]

Tell it to the workers in the video game industry.

[fixermark]

Videogames, in particular, should be a fascinating case study in lack of unionization.

I assume it's because there's always another batch of fresh-out-of-college young people willing to throw their bodies onto that grindstone that we haven't yet seen successful unionization in that space?

[scrumbledober]

I think video game developers are a subset of developers and that subset is almost entirely passionate about video games. Very few people end up working in game development if they are not passionate about it. I think any time you have a workforce who are passionate about their field you can get people to work for less than if they held the same job in a different field that wasn't full of passionate fans.

[simion314]

Do you think the passion keeps them working more then 80 hours a week or there is some pressure?

I worked 16 hours a day for a week, it was horrible, I don't think I can do 2 times more in 16 hours then in 8 and I gave up the money and just worked the 8 hours(now I am doing 4 hours a day , screw the money)

[smacktoward]

Actors' unions do impact salary. Union contracts set and enforce minimum amounts that all working actors have to be paid, for example. An actor earning these amounts is said to be "working for scale."

For illustration, SAG-AFTRA's current rate sheet for TV productions can be found here: https://www.sagaftra.org/files/2017%202020%20wages%20TV%2010...

[simion314]

So isn't ok of setting some minimal salary? I do not see why the developers would be against this, only the companies would like to abuse the developers and work them extra hours and not pay.(so probably companies are spreading the FUD against unions? )

[davinic]

The major benefit of the acting unions is the ability to limit the labor supply. In a growing industry like tech, this isn't necessary as the demand has always been greater than the supply of talent.

[simion314]

Can you explain why do you think that?

I am aware only of actors getting protection from dangerous activities, exploitation, bad work condition.

[mcguire]

https://www.backstage.com/magazine/article/non-members-need-...

[zozbot123]

> Many of the benefits of collective bargaining aren't applicable to people who are relatively easily able to switch jobs or work as a consultant.

The other side of the coin is that collective bargaining itself makes switching to a different employer or working as a consultant a lot more difficult than if the sector wasn't unionized. Sure, some people will have trouble doing these things anyway, especially at the low-end of the income distribution. But that's why we should support policies like Basic Income, or at the very least expanding things such as the EITC and getting rid of e.g. payroll taxes for low earned incomes. And I think that many people here on HN would agree, whether or not they self-identify as libertarians.

> ...particularly in game development, where conditions can often be worse.

Game development is the sort of industry that everyone thinks they'll want to work in, only to change their minds very quickly once they see how the sausage is made. Even just raising awareness about the work conditions in the industry - and making it clear that they're not representative of "tech" more generally - would help a lot.

[freedomben]

Thank you. As someone who worked in a union before switching jobs, it is not all rainbows and unicorns like so many people try to present it. In one shop I worked in, I was a truck driver delivering fuel to airplanes. If my truck broke down in any way, even something as stupid as the key got jammed, if I pulled out my leatherman and pulled it free, I could be fired for violating union agreements. Even most of the mechanics agreed how dumb it was. I was the sucker sitting out in 100 degree summer sun in the airport with zero shade, waiting 30 to 60 minutes for somebody to come do a job that would take me 10 seconds.

That's before we even talk about collective bargaining. Getting a pay raise was completely out of the question, as raises were almost entirely based on seniority and how long your ass had been in the chair. It was highly punitive to younger people like myself. We also got crap shifts because shift preference was also awarded by seniority in the union. The non-unionized shop paid a shift differential, so people willing to work 2nd and 3rd shift got more money for their time. That was a great solution, as it increased the supply for shift work to approximately the levels of demand (basic economics).

So tl;dr: unions have and had a place, but the cure can sometimes be worse than the disease. Acting like unions are this amazing shining solution with no downsides is pure ignorance.

[rchaud]

> Acting like unions are this amazing shining solution with no downsides is pure ignorance.

People are talking about the benefits of unionization in a specific industry in response to the near-automatic narrative that unions are bad.

You gave an example of an absurd regulation in a completely different industry. How does that tie into what collective bargaining in software dev would look like?

[freedomben]

Great question. Of course unions in software aren't really a widespread thing, so speculating at what they would look like is fraught with all the problems of speculation, but this is what I think of:

Currently at work, I'm more of a "devops" guy but I get into things all over the stack sometimes too. In previous places I've been a "backend" guy that occasionally got into the frontend, etc. I view this as the optimal arrangement: blurry lines of responsibility (so people aren't pigeon-holed), but you can still develop depth and expertise in an area of specialty.

In a world of unions, if it were analogous to my past experience, there could be a "front end" union, a "back end" union, a "dev ops/operations" union, etc. These unions would then draw up lines, much like the "driver" and "mechanic" unions did in my past. Need to change a line of javascript? Talk to a "front end" guy. Tweak a deploy script? Not if the union agreement forbids it.

Those seem like ludicrous thoughts based on where we are now. But I'm sure at one time the idea that a driver can't effect any repairs to the truck, no matter how small, probably seemed ludicrous as well. Yet here we are.

I know I probably sound very anti-union, but to clarify my position, I'm only anti-forced unions. So long as I can opt out of the union if and when I please, I have no qualms. Sadly that is not the case in many places in the United States.

P.S. If I could edit and re-word this line, I would. I think the language is unclear and unnecessarily harsh:

> Acting like unions are this amazing shining solution with no downsides is pure ignorance.

I would change that to: "Thinking of unions as all upside with no downside (or vice versa) is an argument from ideology, not one from experience."

[rchaud]

I can definitely agree with your rephrasing. Unions can be large organizations too, and are certainly not immune to bureaucracy and the pursuit of short-term wins over long-term gains for the people they represent.

[Apocryphon]

These are great comments because they underline pain points that 21st century labor unions can work to solve and iterate upon

[rmdashrfstar]

Please keep talking about issues like this. There’s too many preaching a cure from an armchair and not enough recounting actual experience.