For example, seniority requirements and enforced degree or qualification requirements don't sound like something I would want, nor would the many other software engineers like myself who didn't go through the "proper" path of getting a CS degree.
This is example the problem I am talking about. This is a barrier to entry. Instead of being allowed to just apply for a job, and accepting it, you have to "do you time" in a low paid apprenticeship.
This puts up a barrier to entry to new people wanting to join, because union members want to reduce competition.
I am not just talking about degree requirements. Instead, I am talking about any barrier to entry. Unions have a very real and logical reason to put up barriers to entry. It reduces the supply of labor and increases prices for existing members, at the expense of people trying to break into the industry.
You say barriers to entry, I say putting in the time to ensure you're someone I want to work with in the future.
Ok fine. You are free to say that you want barriers to entry and want to prevent people from getting jobs, by making them do all this other stuff.
But other people like me do not want that. We do not want to be forced by a union to do all these things, and instead want to be able to negotiate on our own to get a job.
A union being an unrelated 3rd party should have no say in that kind of business arrangement.
And there are a whole lot of other people, just like me, who would never have been able to get into the industry if we were forced to jump through all these hoops and we will not support organizations that pull up the ladder behind us.
> You say barriers to entry, I say putting in the time to ensure you're someone I want to work with in the future.
Its funny how you are almost directly contradicting your previous statements here.
Previously, you tried to argue that degree requirements, or other barriers to entry are not a thing. And now you are giving reason why you actually support those requirements?
Do you not see the direct contradiction that you made in like 2 posts?
Instead of that, you should have started off by saying "Yes I want there to be requirements, enforced by a union. I want you to be required to get a degree or do an apprenticeship, or a number of other things/ insert random thing X".
But you didn't do that. Instead, you disagreed with my factual claim that there are requirements, which you have immediately now backed off from without admitting that your original statement was wrong.
A union is, in fact, a related second party. It is comprised of employees of that employer. You seem to be under a grave misunderstanding of what a union is. I recommend learning about what they are and put the koolaid down.
You seem to have a grave inability to interpret words to find out what someone's central point is, if you think that anything that I said relied on some definition of what a 2nd or 3rd party is.
I don't care about your word game. What I care about is my ability to negotiate my own job, with my own contract, and to not be forced to follow the union contract that includes barriers to entry by the previous posters own admittance.
I do not think that people should be forced to get certain requirements, or get a CS degree, or any of that nonsense, before they can work in tech.
And playing a word game does not overrule that central point.
Do you have any comment at all on this central point, or is the only comment at all that you have on some dictionary definition of 1st, 2nd, or 3rd party?
We might even get real engineer licensing programs and become an accountable part of society...!
By defined you mean requires as per the contract or even the law.
Yeah, no. We do not want to be forced into your requirements.
And we will fight and sabotage all of these efforts, because we know what it is that you are advocating for, and we will not pull up the ladder behind us.
Fortunately, the anti union side is winning in the tech industry, and those who want enforced barriers to entry are losing so much that none of this is even a real conversation in the industry right now.
> We might even get real engineer licensing programs
So literal legal requirements. Yes this is what us anti union people want to prevent.
This is why you will never has us on board. Because when your mask comes off, and people are actually honest about what they want implemented, it becomes clear that it was always exactly the stuff that we were trying to prevent.
Already trying to lock out the young, energetic, and ambitious using seniority systems? At least you're honest about it.
If you're young and you're considering supporting unionization for developers, keep in mind that people like the parent poster are your future seniors. They're marketing unionization to you to secure their own jobs and then maybe yours as a secondary consideration.
The same also makes it more expensive for you to switch jobs (you lose your seniority), which reduces your negotiating leverage.
I don't have a CS degree either, and I'm not sure why you think labor unions would impose them? Degree requirements come from the company, not from the employees.
Labor organizations lobby for qualifications because it helps people who have them of course.
Additional requirements lower the supply of labor, and therefore increase wages for people who have those qualifications.
An example of a similar union where this is done is in the screen actors guild. They don't just let anyone in. Instead, they require you to do a certain amount of work before you are allowed to join.
The catch-22 of course, is that the union screen actors guild contracts prevent all but a minimal amount of non-union jobs on a certain production, therefore putting up barriers to entry for new people wanting to join the industry.
You need to be in the actors guild to be able to work in the industry, and you can't get into the actors guild unless you've already worked in it! Catch 22.
It all makes perfect sense for the goal of a union to be to decrease the labor supply, thereby helping the existing members.
I'm sure other people can come up with similar examples.
Because unions have often in the past imposed various credentialling requirements, followed by quotas on the credentials given, as a way to push up wages.
For example the UK health system is wrecked by this. Medical unions insist on very low numbers of school places, too low to meet demand, so the government is forced to rely on immigration to fill the gaps. The unions love this because they're all overtly left wing organizations and want mass migration, also they see immigrants as free Labour voters. But being unable to actually train sufficient doctors is a bad place for the country to be in.
A programmers union is too dangerous in this world, especially in these times
However. Governments, and perhaps Unions, are by definition (correct me if i'm wrong?) an entity that is by the people and for the people. Some for-profit company or individual has no ethical obligation to treat workers correctly, fairly, etc. So if we remove unions and government, what power do individual people have?
To that idea then, people need a gov/union to have a voice - but govs and unions also need to be built with an extreme attention to oversight. Which we usually fail to implement correctly. Nevertheless it's the only tool we have - to give individuals power by distributing agreement. So to me the question isn't for or against gov/union, but rather how we can build them to scale and last. Especially in the face of pressure to corrupt.
Happy to hear opinions on where this is wrong, though.
I never heard of this definition for unions! Unions definitely aren't for or by "the people", that would mean everyone. Unions are - by definition - a group of arbitrarily defined "workers" lined up to fight the "management", another somewhat arbitrary group. They are inherently exclusionary and divisive.
Unless you're a communist, in which case you think managers, company founders, shopkeepers, farmers etc aren't really people.
> a group of arbitrarily defined "workers" lined up to fight the "management", another somewhat arbitrary group. They are inherently exclusionary and divisive.
So is _any_ group but "all". "For the people" doesn't literally mean "all people". Government would also not be "for the people" by your definition, given that we have no (real) global government.
If we get together and form a union, ie our joint effort towards a common goal, have we not formed an entity for the people (us), by the people (us)?
Your argument seems odd. "But it's not for everyone" is.. well, yea - nothing is. Literally. What can you say that is "everyone"?
Weird statement. No one is trying to stop you from programming. They are talking about credentials to be employed professionally.
The weird statement is yours when you say they don't stop me from programming. They do!
The other thing that people probably worry about are protecting the net negative members on the team. Those that make more work for the team, derail meetings, block things from being submitted, etc. Nobody wants to hear "well our contract doesn't allow us to fire them".
Like all engineering, there isn't a solution with no downsides.
I think unions deserve serious consideration. Our working conditions are not perfect (know any software engineers with wrist problems, back problems, or sleep apnea?). Our benefits are not perfect (love being forced to take a mandatory vacation every year paid out of my personal vacation balance). And, we have pretty much zero sway among the government. (Do you think that if attorneys were paid in illiquid shares that every time you received them, you'd have to send a hand-signed letter to the IRS?) There is certainly something to be gained; software prints money, and the people that make it deserve their fair share.
Even on HN, commenters are shocked by the FAANG salaries, but you know lots of people are making way more money. Someone just paid $7M for the two story house behind my apartment. I'm guessing they're not a couple of software engineers. Why is that? Is it because we self-sabotage? Is there not that much money in software after all?
Someone should look into all of this, but as long as we see ourselves as individuals and not a group, we will be easy to ignore.
(Uh oh, now I sound like a communist.)
Are these not things you would expect to be able to negotiate on your own? Who are you working for that would rather lose you as an employee than provide you with an ergonomic keyboard?
> And, we have pretty much zero sway among the government. (Do you think that if attorneys were paid in illiquid shares that every time you received them, you'd have to send a hand-signed letter to the IRS?)
This is the most significant thing that unions actually do, but it seems weird to bring them in for the things they're "supposed to do" (negotiating with employers), when you don't really want that (they protect bad team members), because what you really want is something else.
And in that role a union doesn't really fit here, because you have interests shared with people who wouldn't be in it. Even if you have the same legislative goals as every other software developer, what sense does it make to unionize your own tiny startup or small business, or some entity which is already majority-owned by the employees?
Maybe what software developers need is not a union, but a PAC?
that's the thing, software workers are used to just walking away, because their skills are versatile and demand is high. A national level athlete can also simply retire on a few year's funds (or hell, sell themselves as an influencer. You don't think a youtube channel alone of LeBron wouldn't generate a 6k income from weekly "advice"?), but they tend to have a competitive drive to stay in the game, literally. You don't grind your entire childhood's physique away because you're gambling on the chance you retire at 30 (even if that is the most likely thing to happen due to injuries).
To be frank, the vibe I get from the internet seems to be that a lot of SWE's are indeed minmaxing to get out of the workforce ASAP.
But walking away voluntarily is different from having to walk away because your employer gives you an ultimatum. Especially when you're facing a market that has been hit by mass layoffs by many tech companies, and especially if you're looking specifically for a WFH job when many companies are demanding return to the office, precisely reason you'd be walking away in the first place.
Is there a real difference between walking away due to an ultimatum and walking away due to the prospect of better pay or work conditions? Especially in the case where you started pre-pandemic and technically WFH was never indefinitely promised?
Either way, you are voluntarily choosing to seek a better job with better work conditions. The only difference is that you may not be able to be as covert in the ultimatum situation.
> to seek a better job with better work conditions
> The only difference is that you may not be able to be as covert in the ultimatum situation.
The words you use here are interesting: "the prospect", "to seek".
The only difference is that you may not be able to find a better job with better work conditions if you're operating under the gun of unemployment and in a significantly worse job market.
> technically WFH was never indefinitely promised
It some cases it was indefinitely promised, and then employers broke the promise.
The reason to have a union is that no matter how much money you make, the owners of the business have more money and power. Collective bargaining is a counterweight to the power of ownership.
And it's not just about money, it's about working conditions. For example, labor unions could fight back against back-to-the-office demands, whereas without a union, employees are forced to individually consent or lose their job.