3 ms·
I'm sorry if I came across as a snob, I honestly value highly the unions contributions to workers' rights (all workers), historically. I just do not see any fa
by Kurtz79 11y ago
I'm sorry if I came across as a snob, I honestly value highly the unions contributions to workers' rights (all workers), historically.
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 ?
- bryanlarsen 11y agounfairnesses listed in the article: - 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
- kalkin 11y agoDidn't mean to accuse you yourself of being a snob. A lot of people take the same line as you. 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.
- crdoconnor 11y ago>as a group never experienced any need that could be solved by unionizing. * 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...
- johnward 11y agoAdd non-competes to point #2. I know they don't exist in CA but for the rest of us they still do.