There is work that is utility work and there is work that isn't.
I don't mean skilled or unskilled. A common dunk on the distinction between the two is something like "I'd love to see the CEO of <so and so> try a day on the line of <so and so> and see if they still want to call it unskilled labour."
No, where I differentiate is jobs where ANYONE can learn the skills, and others where NOT anyone can. These are by the way not purely academic skills, they are some where the differences are physical, though these days there is fewer and fewer of those as humanity got super good at making tools.
Basically I'm saying there are jobs where maybe the CEO wouldn't be able to figure it out on day 1, but with standard training, they would be able to do the job. And with EXPERIENCE they would be able to get better and better.
These are the jobs where salaries should be set by a union, and where your salaries rise directly correlated with experience.
Now let's get to the classist and controversial part. I don't believe software engineering is like that. Yes, many more people COULD if given the opportunity, and education, and investment. But not EVERYONE can. And not everyone learns at the same pace.
I've been in the industry for 15 years since I graduated with my undergrad, and I've been junior, and I've been senior, and I've seen new grads come in and grow, and thrive, and become promoted to senior. And I've seen juniors come in, and struggle, and tread water, and be managed out. For the exact same job.
I want to be able to promote quickly people who succeed and show an aptitude, and maturity. I want to encourage and incentivize those people to keep reaching for the stars.
I am 100% against unions for software development.