[ryandrake]

I was a wannabe gamedev also, was obsessed with learning 3D concepts, optimizing code, learning assembly language, and so on. After getting nowhere with game companies (You think FAANG is selective?? Try late-90's game companies), my first job ended up being writing GPU drivers for a major graphics card company. Lucked out, I got to work with gaming technology but without the soul-crushing burnout and 80 hour week death marches.

[bityard]

This is honestly one of the best kept secrets in tech. If you actually want some work life balance and don't care too much about job titles and status, the best gigs period are those where you support the "front line" devs in some fashion. Nearly the same pay, but less stress and more self-direction. Tooling and QA folks rarely get called up at 3am on a Sunday morning because prod is down.

[rollcat]

> Tooling and QA folks rarely get called up at 3am on a Sunday morning because prod is down.

My (devops) team did the tooling, but we've worked very closely with QA, and while they didn't get the pages, both teams felt that they shared the responsibility of making the final product (well basically a cool tech demo) rock solid for the viewers. In 4.5 years there I've touched ca 600 projects, but I agree with you - it was still easier than doing the frontend work. Arguably less glory but definitely more life.

[Quikinterp]

I wonder if some AMD folks did last week when their latest drivers caused players to get banned in counter strike haha