Not looking for pro- or anti-union sloganeering, but real impacts. The economics of the tech sector would change dramatically with organized labor in computing, and I'm interested in how those changes would manifest.
Not looking for pro- or anti-union sloganeering, but real impacts. The economics of the tech sector would change dramatically with organized labor in computing, and I'm interested in how those changes would manifest.
Going by what happens in other industries, you'd reasonably expect a flattening of wages (both inter and intra firm) and an increase in the average wage. You'd also expect entry into the field to become harder, and exit from the field (both voluntary and involuntary) to become rarer. Fewer workers would be employed overall, though per capita productivity would increase; the overall effect would probably mean more money allocated to labor, less to capital holders, and higher costs for consumers. Work rules would increase, e.g. no one allowed to be on call for more than X hours a year, or a SWE not being allowed/required to take on job responsibilities outside the scope of the initial job offer except as facilitated by formal processes.
Many of these effects will disproportionately benefit women and racial minorities (this is a rare case where "racial minorities" includes Asians of various sorts, as they're paid less than white people in the field, though that's in large part to the power employers have over visa holders).
This was a great answer I've read several times as I consider organized labor in software development regularly. Thanks for giving me targets for research.
Management knows that already, so they'll do whatever they can to stop unionization. Retaliating against attempts to unionize are illegal, but internal anti-union propaganda campaigns are common in other industries, and I think you can expect not just what already exists, but better-funded campaigns and targeted to people more like you.
Management would also try other methods to get around the union. More outsourcing, contracting entire projects out and requesting documentation or support contracts. These don't work well - they always cost more than expected, take longer than expected, and are a pain to maintain - but they do work some, so with unions raising wages that'd move the bar towards a little more outsourcing. I'd also expect it to take management a while to relearn that outsourcing doesn't work very well, since it's been a while. Many companies will be willing to pay more for outsourced labor than union labor, because strong unions are a long-term threat to the investor class. If the union covers multiple companies it'll be more resistant to all of this and generally more effective.
The effects on the workers depends on the union's goals and determination. The biggest test is its first strike; how many employees actually go through with it and how long can they last. That depends a lot on the strike fund; even though we're a wealthy industry that should be able to make a strong strike fund, I'd expect a lot of programmers to be suspicious about it (then again I've heard more union talk this year than I have in the rest of my career combined, so maybe they're coming around). I expect the union will achieve all of its goals, as software engineers will drastically underestimate how much striking power they have. Judging by conversations I've had, I'd expect priorities to be: major commitments to privacy/security/ethics/maintainability, improved working conditions (less dense open offices, maybe an end to open offices), and maybe more vacation time. Increased pay seems to be a low priority among workers I've talked to.
Employers will likely react I a counter productive manner to this threat - e.g. mandating 100% unit test coverage which would be achieved with cryptic tests that actually make the code even harder to work with.
This could lead to a decline in overall software quality in America if the relationship between developers/ops and management really sours.
Afaik you’re allowed to stay in the country as ling as you are employed by the employer on your visa regardless of whether you are working or not.
Can you be fired for going on strike?
You are still employed, you're just not getting paid. There are laws that state, in effect, that you cannot get fired for going on strike as part of a lawful strike. Well, if you aren't fired, then you must be employed, right?