I always wanted to program games. I programmed games as a hobby. When I graduated university there were no gamedev jobs in my region, so I went to work at Boring B2B java company.
After a while I moved to a bigger city and I started having friends who work in gamedev. They told me about crunch, bad salaries etc. I decided to keep doing Boring B2B stuff. But I went to a few job interviews in gamedev companies.
Every time the questions on the interviews were FUN. Like doing 3d math, some low level C, writing a collision detection function or simple pathfinding.
Just solving these problems made me giddy.
Maybe it's the nostalgia for the time I've learned these things as a teenager with no stress, or maybe it's just that it's something completely different to what I'm doing normally - but I felt great during these interviews.
But I'd have to get a huge salary cut and abandon work-life balance and I'm too old for this.
TL;DR: I think there's a lot of value actually looking at day-to-day problems you need to solve in your dream job, even if you decide it's not for you for different reasons.
I read their comment as saying that we shouldn't expect every subtask to be fun, but the overall task can still be fun. Do I want to sand wood? Not really. Do I want to grab sand paper from the drawer? No... Do I want to use a saw? A little bit. Do I want to build a chair? Yes! But if I break it down too much the overall big picture gets lost.
thrwwXZTYE|7 months ago
After a while I moved to a bigger city and I started having friends who work in gamedev. They told me about crunch, bad salaries etc. I decided to keep doing Boring B2B stuff. But I went to a few job interviews in gamedev companies.
Every time the questions on the interviews were FUN. Like doing 3d math, some low level C, writing a collision detection function or simple pathfinding.
Just solving these problems made me giddy.
Maybe it's the nostalgia for the time I've learned these things as a teenager with no stress, or maybe it's just that it's something completely different to what I'm doing normally - but I felt great during these interviews.
But I'd have to get a huge salary cut and abandon work-life balance and I'm too old for this.
TL;DR: I think there's a lot of value actually looking at day-to-day problems you need to solve in your dream job, even if you decide it's not for you for different reasons.
megaloblasto|7 months ago
brazzy|7 months ago
megaloblasto|7 months ago
missingdays|7 months ago
Do you think nobody wants to write and debug code, or tend to plants, or write books, day in day out?