110 hours total clocked for a week is pretty bad, but thankfully he only experienced that once. Not to say that his experience during crunch time was bad, but I've heard of much, much worse than this. Consider seven days a week, for three months straight!
he could change to be a developer and get to experence those sorts of conditions more regularly. can be a bit scarry seening the degredation in the quality of code programmers write with lack of sleep though.
Theres no excuse for these type of hours, its 1 of 2 things, greed or mismanagement.
I've been very lucky that all the projects I have worked on have had very little crunch overtime, no more than is reasonable considering the nature of games.
110 hours total clocked for a week is pretty bad, but thankfully he only experienced that once. Not to say that his experience during crunch time was bad, but I've heard of much, much worse than this. Consider seven days a week, for three months straight!
he could change to be a developer and get to experence those sorts of conditions more regularly. can be a bit scarry seening the degredation in the quality of code programmers write with lack of sleep though.
Theres no excuse for these type of hours, its 1 of 2 things, greed or mismanagement.
I've been very lucky that all the projects I have worked on have had very little crunch overtime, no more than is reasonable considering the nature of games.
110 hours total clocked for a week is pretty bad, but thankfully he only experienced that once. Not to say that his experience during crunch time was bad, but I've heard of much, much worse than this. Consider seven days a week, for three months straight!