3 ms·
The real problem is that the game industry is project based, but pretends like it isn't. Start a project, swell the staff, ship the project, shrink the staff. I
by bane 13y ago
The real problem is that the game industry is project based, but pretends like it isn't. Start a project, swell the staff, ship the project, shrink the staff. If they're lucky the next project will along in parallel and soak up the staff and the rest are "surprised" that this has happened.
The movie industry should be the same, but it isn't because outside of a few key people working the project (the actors, directors, producers etc.), almost all of the rest of the people are hired in via contract to production companies. So an SFX house or a Foley studio can keep their staff working on several projects at once and not have to go through as much of the hire/work/fire cycle. Cameras are rented from equipment companies and camera operators are similarly contracted.
So when you go to make a movie, the studio hires the key staff, then contracts out pretty much all the rest of the work to companies like Maslow Media Group or whatever and you get vetted professional tradespeople who come in, set up, do their job, and then move on to the next gig their production company has lined up for them. So their layoffs really only happen when the entire industry takes a hit.
In the game industry, they're still learning this lesson. There's a few places where outside contracting exists, mostly in sound design and music and middleware developers (various engines or tools), but that's about it. They still hire on teams of developers and artists, build the thing then fire all of them.
- Sivart13 13y agoIsn't "come in, set up, do their job" most viable though if you're local to the project? I imagine a lot of the movie industry work takes place in LA, whereas game development work is spread out all over. You could imagine that remote work might help in this situation, but I've heard stories about the difficulty of communicating artistic vision across geographically disperse teams.
- bane 13y agoYeah it's true, but I don't know if it makes a difference in this case. Game developers are already working in locations that have big studios. They work for EA this year, get laid off, go work for somebody else next year, get laid off work for EA the next etc. They're already more or less there. It'd make more sense for them to work for a "Sivart13 Melbourne, Co., Ltd." and contract out your group of developers to whoever so they maintain employment. Instead of going through expensive and time consuming HR processes every year, the publishers could just go through half a dozen contract negotiations instead. One well known example of this model is TOSE, https://en.wikipedia.org/wiki/Tose_Co.,_Ltd https://en.wikipedia.org/wiki/Tose_Co.,_Ltd.