You succeed at programming by spending countless hours on your own with a computer. Your career is a direct result of your own hard work and passion. From that perspective, organized labor seems like an unnecessary dependency. Programming is a form of extreme independence many will be hard fought to give away.
I don't know if this is true. My career is also a result of the excellent mentors I have and continue to have, the wonderful peers I cooperate with, the selfless professors who taught me fundamentals, the excellent technology already built by those who came before me, etc.
I really can't say that my career is a result of my own hard work and passion as if my own hard work and passion is the primary thing that allowed my career to succeed. It doesn't matter how passionate and hard working I am if my environment wasn't condusive to computer science as a profession.
Tech makes an alternative path available to others though. You can be a self taught programmer and become very successful. It's one of the only fields where you can achieve an upper middle class lifestyle without accreditation. You'll definitely be working hard to make that happen though.
I couldn't be self taught without learning materials that others have produced, the programming languages that others wrote, or the technology that others built.
I'm also not speaking mentors and peers just in school. I mean literally I do not believe I could be self-taught with 0 outside mentorship or learning materials or community and be considered a highly successful developer. I needed learning materials and mentors to teach me best practices in software development. I needed programming languages that I didn't write myself. I needed a computer, whether paid for by myself, family, or the public taxes via libraries.
Not stopping to recognize that I program on the shoulders of giants would make me arrogant and foolish, I think.
That said, such independence can be taken away just as quickly by the megacorps through all manner of illegal dealings and anti-competitive practices. We worked hard to earn the money we do, it's our right to defend ourselves against another "no poaching" agreement or, god forbid, another attempt to use our hard-learned skills to support the oppression of others.
> You succeed at programming by spending countless hours on your own with a computer
... which requires access to time and computers to train on. Not everyone is quite in that state. And not everyone is an autodidact either, it's not the only valid route to programming.
> Your career is a direct result of your own hard work and passion
Not completely - it's a result of getting accepted by hiring managers, and then retained by internal performance processes, both of which are incredibly subjective and vulnerable to prejudice.
Moreover, some people care about things beyond themselves. A key component of unions is solidarity: caring about how your colleagues are treated. This may also extend to how your employer is treating the wider society.
> Your career is a direct result of your own hard work and passion.
If your code isn't using your own libraries compiled by your own compiler hosted on your own OS running on your self-built machine using a CPU you designed, no, it isn't. Sure, your own hard work and passion goes a long way but you rely heavily on the works of others and the privilege of being able to use them.
This is an unproductive reductionist gatekeeping response to a genuine description of the effort and toiling many have gone through to reach their position.
I'm developing in 2019. If I was developing in 1976 I would have been working on something much farther down the stack. Either way requires an immense amount of time in front of a computer to be a top performer and in either time period putting that time in would lead to success.
But people who developed those libraries allow anyone to use them, so you have the same chance as yor neighbor to develop the next Google, and there are a lot of smart people trying to do it, and not all of them will succeed.
So, your career is a direct result of your own hard work and passion.
That assumes you're starting from the same place and head in the same direction. You have to know a library exists before you can use it. It has to be compatible with what you're using. There are many things out of your immediate control that can influence these things (imagine my next door neighbour only has an i3 and the fancy functions of the library which make it 100x faster require extensions of an i7. I immediately have an advantage. There are many subtler advantages that can come into play.)
Developers (some) aren't super-conservative, they're libertarian.