this post was submitted on 16 Aug 2023
1390 points (96.2% liked)
Games
32663 readers
1035 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can't understand why crunch time has become so normalised. There's no other software development project where constantly failing to plan for the needed time requirement would be accepted. Crunch is a sign of bad project management, it isn't normal.
But when it works, when that day comes, weβll make a hell of a lot of money for the shareholders! Isnβt that nice?
At some point, people figured out that during a couple of weeks of mad rush right before a deadline, if you've got committed, well-rested employees who know they're going to get a rest afterwards, they tend to be much more productive than they normally are. Some bad managers only paid attention to part of that, and determined that eighty hour weeks are more than twice as productive as forty hour ones, and intentionally started inducing crunch. They somehow didn't notice that the third week of crunch is only about as productive as a regular week, and after that, it's way less productive as everyone's exhausted. Combine this with the fact that people with management knowledge tend to flee from the games industry rather than to it, and you end up with the software engineering industry's least effective managers running things with easily debunked dogma.