this post was submitted on 02 Mar 2024
329 points (96.9% liked)

Games

32501 readers
2220 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:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. 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
[–] [email protected] 1 points 8 months ago (1 children)

Not every dev is compiling code to run on a devkit

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.

surely they are not running a new build every day.

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.

[–] PickledEggs 2 points 8 months ago

If you don't run new builds contantly, that means you aren't doing any actual work if you are on the engineering side.

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.