I've read lots of stories about "endless death marches" in game development. Have you experienced this or heard about it? Is it any worse than any other software jobs.
Something that has made me shy away from game development is that I'm not a big gamer myself and it seems like there are enough diehards that a fairly casual gamer like myself just wouldn't find the commitment to follow through. What would you say to that, and it's okay if the answer is "yeah, you should probably be a gamer".
1.
Ah yes the endless death machines they're a bit of a pain. I find in general development there can be these but in game development it's a whole lot worse. With working in games editing one value can sometimes change more than one thing in the game itself so fixing a bug has to be done very carefully.
2.
I say to people it's okay to not be a die hard gamer if you're a game developer. It's obviously great if you are but developing a game I find is more community based seeing as they're the ones that are going to be the ones playing it the most.
In addition research into the type of game you're going to be making will always be an essential part it of it. If you're working on a game that is somewhat similar to lets say overwatch your employer would be expecting you to play a fair bit of overwatch to see how the game works, get a feeling of the mechanics, see how players interact with one another.
Personally I don't think you'd need to be a massive gamer, as long as you're willing to learn about different games cultures, different communities and interact with the community you're in you should be fine.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've read lots of stories about "endless death marches" in game development. Have you experienced this or heard about it? Is it any worse than any other software jobs.
Something that has made me shy away from game development is that I'm not a big gamer myself and it seems like there are enough diehards that a fairly casual gamer like myself just wouldn't find the commitment to follow through. What would you say to that, and it's okay if the answer is "yeah, you should probably be a gamer".
1.
Ah yes the endless death machines they're a bit of a pain. I find in general development there can be these but in game development it's a whole lot worse. With working in games editing one value can sometimes change more than one thing in the game itself so fixing a bug has to be done very carefully.
2.
I say to people it's okay to not be a die hard gamer if you're a game developer. It's obviously great if you are but developing a game I find is more community based seeing as they're the ones that are going to be the ones playing it the most.
In addition research into the type of game you're going to be making will always be an essential part it of it. If you're working on a game that is somewhat similar to lets say overwatch your employer would be expecting you to play a fair bit of overwatch to see how the game works, get a feeling of the mechanics, see how players interact with one another.
Personally I don't think you'd need to be a massive gamer, as long as you're willing to learn about different games cultures, different communities and interact with the community you're in you should be fine.