* Breaking Apple and Google's wage fixing cartel.
* An end to those bullshit contractual terms that state the employer owns everything you dream up in the shower.
* Legal help with companies that promise the world with options and then shaft you later with fine print.
* Lobbying to trash software patents / H1B/indentured servitude visas.
* And end for stack ranking
I could go on...
- stack ranking
- binding arbitration
- non-competes (outside of California)
- IP assignment
- mandatory inclusion of performance reviews in a candidate’s transfer packet for internal mobility
- severence pay
I think the linked post describes some issues that could be addressed by unionizing - arbitrary management and degrading ranking systems. You could add secret non-compete agreements to cap salaries (which are not too far from that pre-free agency baseball case) and gender and race-based discrimination in hiring, pay, promotions etc.
I just do not see any factual reason for a "SW developer union", since it is a very modern role, and as a group never experienced any need that could be solved by unionizing.
As you mention for the case of baseball players (or the actors, in another post), the union was made during a period in which the current work conditions were not seen by the category as fair.
Do SW engineer think it is actually so, today ?