Thanks for the insight into the world of game programming. I should really go to these conventions run by Epic (when there is one in the UK) to discuss it more.
There are people in my world who are just the same, writing variables and properties as “a,b,c,d,e,f” is just irritating to read.
What I would say though. From what you have written about game development cycle practices. It is no wonder that almost all games these days require a patch on release (day 0/day 1 patch), it sounds like a mess to me!
I get hassled daily by recruitment consultants. They all feel that way!
In my profession, most companies (in the UK anyway) do want blood from a stone! I have to know around 10 separate technologies and javascript libraries otherwise my CV is scrapped or the interview process fails. I wouldn’t of thought that the game profession would be any different in this aspect and judging by post, it isn’t.
Back to the original post. I turned down a junior-mid level position (working in Audio Tools Department) at Rockstar Games in Glasgow when I was about 24-25 because I was too afraid of the big change of moving 300 miles away (stupid mistake, hindsight is wonderful). Are you talking about developing an indie game for yourself or just becoming part of a games development company?