>>715713778 (OP)
The 2025 development cycle for any software is >hire devs to make a product on tight schedules >abuse them as much as possible >product releases >success or failure the dev team is laid off anyway with some excuse for no bonus >hire team of Indians to do maintenance until next product where the company either implodes or successfully swindles a new dev team to join in and hopefully offset the mess the Indians made >cycle repeats
>>715713865
Bleeding talent constantly is clearly a good business strategy.
That’s why good studios find ways to retain talent, either with smaller projects in-between big releases, or timing larger releases to allow the bulk of the team to roll over into the new one once the old one ends
>>715714094
I don't know how many worked on Oblivion but this was only 7% of their employees, they're a massive support studio, worked on over 1500 games
>>715714001
more like >hire contractors >run them into the ground >fire them >hire new contractors >run them into the ground >fire them >repeat 1000 times over 5+ years >only 2 guys have worked on theproject for the entire time >decide releasing now would be more profitable than hiring another batch of contractor to finish it >release >1 of the 2 mainstays is now the entire support team and the other gets fired.
So, what's the level of success you need to not be laid off by Microsoft because it seems no matter if you do good or bad you're getting laid off either way.
>>715714090
The company I work for is in chronic hemorrhage because they let people go as soon as they realize they won't have anything to do for a few days.
It's my turn now. I lasted two years and two weeks.
>>715715696
its almost like they mass fire and mass rehire every 12 months, I wonder why.
can't be something to do with tax or money laundering or something shady.
those employees were just eating up resources!
>>715713865
If you're only hiring for the project and don't need them afterwards then use contractors with clear end of contract so people don't just get the rug pulled out from under them.
>>715715696
You need to know someone and/or make it into their core team. Companies are moving more towards temporary hires and outsourcing to cut costs. Also, AI.
working for game companies seems to be a shitty deal, worse salary than some average tech company with probably easier work less hours. even some boomer company is better
if you really want to make a game, make your own one on your own time
>>715713778 (OP) >Hire studio to do a job >They do the job >Deliver game to publisher >Their job is done >Studio no longer needs 300 of their staff
I mean sure it sucks they lost their jobs but isn't it the people running the studio that needs to secure regular work for their studio to survive? Construction works in the same way which is why projects tend to run long.
>>715715930
Saw a video by luke stephens and basically it just boils down to yearly reports where execs have to always report that the company is reducing costs and downsizing because is always attractive to investors. They dont care about employees because they are just numbers on a chart. They overhire people for the sole purpose of being trimmed fat on their operation report graphs.
How many people do you realistically need to port a 20 year old game to UE?
All of the ground work is already done. A jeetsarmake should require maybe ten indians tops.
>>715713778 (OP)
The fact they even had 300 people to layoff in the first place from producing slop like Oblivion Remastered is indicative of just how shit the industry is right now. They should lay off even more people.