Just going to point out, everywhere, I have ever heard of a union it generally made it harder for new people to come in, not easier, by increasing the commitment an employer is expected to make to an employee, and by making it harder to remove employees that need to be removed but can't because of their seniority with the union.
My observation has been the opposite. I believe because the unions have an interest in increasing their membership, not letting it atrophy and decrease due to time and deaths. A union that doesn't have a growing membership is a union that will disappear.
In fact, some unions I've seen have teams of people (including lawyers) whose sole purpose is taking illegal immigrants working in their industry and getting them properly documented and teaching them English for free so that they will eventually join the union.
Where I have seen this is in carpenters, bartenders, maids, food service, stagehands, and a few others. The industries you've seen may be different.
Similarly the economy moved toward services and unions didn’t prepare for that.
Three unions ossified, became political and self-serving (not looking after their workers solely but looking after the org for its own sake and its bosses.)
My original point is the old unions have no leverage not to acknowledge this and accommodate the concerns of a newly union members in a freshly industry.
The way it seems to work is that a contractor wants N number of electricians for a contract, so the first N electricians in the queue are laid off get dequeued and sent to work.
This is a really interesting system, and I think if there were subgroups of software engineers it would pretty much work fine. I think at the end of the day, SWEs tend to be picky about where they work, and employers tend to want SWEs with backgrounds that perfectly match their needs.
I dunno, I think if someone could figure out how to make a queueing system work, it could work for a lot of people and businesses.
It seems close to the agency model already. Only problem is, I don't see how you're going to get top engineers to join. Most of them are already making bananas money, and I don't see how highly compensated engineers would fit into this model at all.
You appeal to their boredom. FAANG pays people to not compete more than anything. Rotation is a chance to break the monotony and actually be able to steer the ship for a change.
It really depends. The smaller the organizing unit, the more short-sighted they're going to be because they have less leverage and they benefit less from long-term big picture thinking. For example, if I'm a union that organizes machinists specializing in a specific type of tool then my focus is going to be on keeping this tool in place and these machinists employed, even if it's at the expense of new entrants or generational changes in technology. If the union is organized for an entire industrial sector, though, then their focus is on organizing and developing labor rights and practices for the sector as a whole rather than any specific shop.
I was basically thinking about my present company that has done a great job of bringing in coops from local universities for work terms. We've had a great experience with this. However, this is one of the only games companies I've worked at that does it.
However, unions increase the value of jobs. Union workers enjoy a better QOL and career stability, and they can actually build a life for themselves without worrying about being fired on a whimsy.
Luckily for something like game development, it is a growing industry with a low barrier to entry. Finding a job or starting a new company is very realistic-- until the next economic downturn, which will hurt union and non-union workers alike
Maybe at a place like Valve, but that's a special case. a private company swimming in cash and having basically zero urgency to innovate or produce even derivative content.
I'd imagine unions are most prevalent in industries with a surplus of workers.
If you have a rapid growth industry with competitive hiring practices, you're probably getting treated great and courted to switch jobs for higher pay pretty frequently.
If your industry is stagnant and management is constantly trying to replace you with less expensive workers that can be quickly trained to do the same job I can see why there would be a strong desire to unionize.
In that sense, I can see how the union would be protecting it's workforce by stemming the inflow of new employees. The fewer the supply of workers, the higher demand for the one's you have.
lol
Less open jobs because people aren't switching every 18 months doesn't sound like a bad things.
What they do do is make it harder to get rid of experienced people and replace them with cheaper ones.
Oh hell yeah.
I did 3+ years on a title, nearly killing myself to ship it. When I realized that doing that much OT was doing to my personal relationships, health and sanity I left with a generous transition ~8mo before ship(including tossing 2.5mo of PTO because they didn't have to pay it out and I could never take it).
Listed under "special thanks" as well, it would have cost them nothing to do proper crediting but instead a giant middle finger for "betraying" the company.
There's so many aspects of that industry that are messed up, I heard similar stories across the board form co-workers at the places they had worked at. Since everyone had gone through the hazing process it was a self-perpetuating cycle that didn't stop.
How much does this matter? (Really asking, I know nothing of this industry, nor film.)
What I mean is, beyond enjoying seeing your name, does it make a big difference in landing subsequent jobs to have your name publicly listed at this size / under this heading / etc. on past work? Do companies hiring you go and check what you say against the credits, or how does this work?
First game I got credited on opened up a ton of doors because everything in that industry is based on what you've done and not your qualifications.
The argument against you getting a full credit is that it would list your contribution to the game as the same as a colleague who worked through the ship process. I'm not sure how it works in the production side of the film industry but I imagine it is not dissimilar.
You definitely did the right thing by getting out and looking after yourself and those around you. The industry has and is responding to the loss of good people due to burn-out, not at every developer but some of the most notorious have realized the level of churn hurts their ability to hire and retain the best. The more push-back there is against the onerous work practices the more quickly they will stop.
There should be universally-agreed rules around how crediting works: how about a case where a noob who joined a month before shipping gets credit, but someone who slogged for 2 years but quit gets relegated to "Special Thanks" despite putting more effort. Does that seem fair to you?
From the game company perspective making the new employee feel good is better than making a former employee feel good.
What is interesting with games that are live for multiple years is how often should in-game credits be updated and how do you credit over time as people join and leave the product with differing amounts of tenure and influence.
But yes, universally agreed crediting rules would be wonderful. I don't see how the collective industry gets there outside of a union pushing for it.
Authors get credit for their books. Everyone who works on a film gets credit for their contribution. This goes into your CV, resume, IMDB, whatever. It's important.
Having an industry approved crediting scheme would be wonderful but for the most part the only people viewing it is going to be people on the credits. No games industry recruiter looks at a resume and verify names against the in-game credits (or even IMDB) - they will check against references and people they know that you may have worked with. Same as every other job application.
Film may be the last industry where everyone involved still gets credited. TV credits are basically unreadable, streaming music credits only cover the artist, books only list the author.
I'm not arguing against credits, just that they are not important outside of being a cool 'thank you'.
So it's fine if you don't care, but plenty of other people do care about getting credit for their work, and to them it is quite important. This describes most people in many industries. So yeah, it is important.
It's incredibly disrespectful to sweep away the efforts of workers that are responsible for the product and to pretend it didn't happen.
I don't know about films, but credits on TV shows apparently work more like lifetime achievement awards than like a list of who worked on what. Everyone touches a lot of different things, your total contributions are tracked informally, and when they exceed a certain amount you get an episode credit. You need to have touched the episode, but you might have done much less work on that particular episode than a dozen uncredited people.
Source: Mark Rosewater's writing about his time on Roseanne.
Also this was a boxed retail title with no dlc so the credit list was pretty fixed.
I'm out of the industry now with no plans to ever return but the whole process just seemed pretty and spiteful. We worked just as hard during those 3 years as I did shipping other titles before that so I don't really buy that leaving early changes the title on which you worked as.
I find it’s more than people only get one shot to organize their project, and it’s scarier to try something you haven’t vs something that was extremely painful but delivered. There’s a large contingent that believes without massive overtime and crunch a game will never be released.
This is something open source gets right that companies don't -- in open source, there is a credits list. Both in the contributors listing and in the actual publicly accessible history of commits itself (which in turn auto-generates contributor lists e.g. on GitHub).
I'm an example myself, as I started in the industry working on a strategy-genre game, and talking shop about the genre makes me more appealing to studios that serve that.
Google, on the other hand, appears to be exactly opposite [1]. So, it appears that, for somebody who worked on Gmail and pursuing the similar line of work in a company similar to Google, proofs of experience would be of little value.
1. https://www.quora.com/Whats-the-logic-behind-Google-rejectin...
That distinction is where some of the wish for credit comes from I believe.
Instead I have a resume and references which can be checked to determine if what I'm saying is true.
Now being able to do that automatically is great, which means we should just take the whole process on our own hands as software developers and create something that represents us?
That said, insurance costs, too, but most of us have it...
The whole point of a union is so that the benefits outweigh the costs but the actual benefits are hard to measure experimentally.
I would say anecdotally that in the majority of cases it's worth it, but the perception is biased towards it being not worth it.
Personally I haven't done a day of overtime in seven years and I feel reasonably compensated but there are clearly other places out there that are still exploiting their workers.
Improving worker input into production schedules and creating clear guidelines around overtime compensation time would probably reduce companies that rely on "crunch time" too much. Over time is ok if the work needs to be done, but workers should have a reasonable expectation of knowing how much of a break they'll get after. Not that it's some random (small) number in their managers' head.
There are plenty of other workplace issues aside from over time and wages that a union could help address.
Increasing transparency and input from workers into company finances and road maps, improving hiring practices, creating more opportunities for young new grads to break in, increasing diversity.
Standardizing crediting would be one close to my heart.
One time I was laid off from a company along with hundreds others due to various company issues, and eventually the project I was working on made it to market. I made it into the credits, but instead of having a "software engineer" title and naming the significant feature area I worked on, I was reserved in a long list of "Special Thanks".
This sort of thing is totally unacceptable. Would be an area addressable by an industry union.