the solidarity i'm describing would help you see how you have the same interests as an amazon driver or warehouse worker, except you get paid a lot more with better working conditions. your dissatisfaction with coworkers and leadership sound like interpersonal problems that will happen in any organization regardless of power structures.
Do you have the power to negotiate for remote work, or to work somewhere without an open office floor plan? There are always areas to be improved upon, practices that management dictates by fiat and everyone accepts as "just the way things are" even if they don't like it.
There would be some really "interesting" technical consequences too. I think we'd commonly hear things like:
"USW-local-42 has used TurboPascal since 1987, and it's worked _fine_ for every project ever since. Bob could have retired at 65, but he's 78 and he's taught thousands of underlings how to master the language. That project that took 12 years wasn't our fault, it was torpedoed when collective bargaining negotiations failed and our whole union had to learn C++. Keeping with the same language is a core tenet of our union and keeping people like bob among the most satisfied employees in $UNION_STATE."
"We at USW-42 only connect to signed APIs from other union shops, we will not support FOSS unless the whole chain has been verified that it has been grown organically from employee-first union-run companies. I know that a 25ms auth check on each call is slowing us down, we have guys working on that. But the law about to pass is going to make it illegal to circumvent these checks. You got to remember, these checks help secure jobs, and there's always going to be trade offs. You can hire us to remove the API calls and re-write the software if you absolutely need that speed up, but for now, think of the children of all these union members who depend on your support and compliance".
