this post was submitted on 02 Mar 2024
328 points (96.9% liked)
Games
32663 readers
1549 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
Tbh, game studios often require special equipment such as dev kits and high-end PCs for development. It makes sense that they might not want to send this equipment home, especially if it is an unreleased console"s dev kit. Game studios honestly seem more justified in not having WFH
Not every dev is compiling code to run on a devkit tho? Also, not gamedev, but surely they're not running a new build every day
Depends on the studio. There will be a lead platform, and if that platform is a console, then a majority will run on a devkit.
In the studio I worked in, we ran new builds almost twice a day. That doesn't include the iterative changes you make if you are a programmer. If you don't run new builds contantly, that means you aren't doing any actual work if you are on the engineering side. If you are in art you might not really screw around with too many builds. If you are a director or producer, you might not either if you're bad at your job.
This is not true. There are higher-end engineering positions that orchestrate everything for the other engineers, amongst other things.
I'll be explicit in regards to my other comment about remote working for others without gamedev experience. Compiling/generating/deploying game-builds is done locally at the studio, but the process is controlled remotely by the game devs.