And the easy (but unsatisfying) answer is: every local is different.
So, what must one know to join a "programmers' union"? Or what can a company expect from a "unionized programmer"?
Scoring's changed, you can simulate a whole orchestra right there in your laptop long before committing to hiring an actual one. Or you can do any of the many things that has changed music since samplers started becoming affordable in the eighties. Also editing's easier.
Acting's changed, what used to always involve getting together in the same place with everyone else in a scene can now just involve hanging out on a green screen stage, pretending that a crude puppet standin is the other person in the scene. Or you might be wearing a motion capture rig that'll be used as the basis for a photoreal animated character who'll end up being composited into the shot over you.
Animation's changed, now you're as much a technician as an artist, you may be expected to pick up a new software package for a new production. Personally I left the animation industry in part because it looked like all my future gigs were likely to be on a software package I kinda loathed.
Directing's changed, you need to be aware of all these possibilites, maybe you decide to not use most of them, but if you do, you get to talk with the people who know them in more detail and figure out how to use all this power.
Big movies are now waterfall projects - everything is preplanned. As one ILM guy said, a Star Wars movie is three years of preproduction, three months of principal photography, and three years of postproduction. Movie directors now are more like animation directors - they storyboard, they plan, they previsualize, they have a full previz version created, and only then do they get the green light for full production. Upper management gets to see all this work, so there's more interference from above.
The same thing they already expect from a non-unionized programmer? Why would anyone expect anything different?
Should a hospital expect something different from a "unionized Nurse" instead of a "non-unionized Nurse?"
While nursing certainly chanes over time and is a difficult job, a good nurse from a decade ago could likely get up to speed within a week or so.
Given the pace of change in coding, I don’t think ai could say the same for a decade younger version of myself.
Also, I contend a good programmer who's been out for 10 years still has the ability to be a good programmer. Sure, they're not going to know whatever language/framework is popular this week, and they'll probably be slower to pick up a new one than somebody who's up to date, but I contend they'll be productive in less than a month.
Honest question: how many of them are used in game development? My limited understanding is that the majority of games still use more traditional languages like C++ and Java.
I would love to see a unionized AWS -the whole org., from top to bottom. Then see if MS or Goog would approve,
And the c++ of a decade ago is quite different from today.
Sounds pretty reasonable to me, if I'm not explicitly being paid to be on call work shouldn't be contacting me.