Just a couple of questions: 1. I read that the Game Development industry is an industry where you get paid "less than average salary, and work a lot of hours a week" etc, is that true? 2. My goal is to rise through the ranks. I want to start as an AI Programmer, then move to Lead Programmer, then move to Technical Director. Is it true that as a Lead Programmer/Technical Director, you need to know all aspects of programming within game development? 3. I heard that it's hard for some to get married in the game industry due to long traveling. Is it true that (I know that depends on location, so I'll ask your opinion) that you may have to commute "30 miles or more" to your job location? 4. When raising through the ranks (etc. I know to be considered a Senior Programmer, you need like 8 years of programming and shipped 4 - 5 games, usually) how many years do you need apart. Like to change from being a senior programmer to being a technical director. 5. I'm going to a Computer Science major in college. How will I learn to apply this in game development? Do jobs generally offer on spot training? I have a real passion with programming and gaming, so I'm hoping to become a Technical Director at the end, and really become involved in the game making progress.

Quote: Original post by Phunin
1. I read that the Game Development industry is an industry where you get paid "less than average salary, and work a lot of hours a week" etc, is that true?

No. You will probably learn less than other software developers, but you'll still earn more than a large portion of the population given similar experience and seniority.

Quote: 2. My goal is to rise through the ranks. I want to start as an AI Programmer, then move to Lead Programmer, then move to Technical Director. Is it true that as a Lead Programmer/Technical Director, you need to know all aspects of programming within game development?

Define "know." I'd say you need to understand the constraints of the various aspects, so that you can allocate resources and manage the team appropriately. Once you've started on your career path, though, you'll be in a position to observe and learn from actual leads and technical directors. I wouldn't worry about something that's several steps ahead of where you are now.

Quote: 3. I heard that it's hard for some to get married in the game industry due to long traveling. Is it true that (I know that depends on location, so I'll ask your opinion) that you may have to commute "30 miles or more" to your job location?

That's absurd. Your commute, in any city, is a function of where you live and where your office is. Why would one industry consistently have particularly long commutes? Visit GameDevMap and look at the studios in any city you're interested in. Visit their websites, look for their street addresses (check the About Us and Contact pages), and see if they seem that far from any reasonable residential neighborhoods in town.

Quote: 4. When raising through the ranks (etc. I know to be considered a Senior Programmer, you need like 8 years of programming and shipped 4 - 5 games, usually) how many years do you need apart. Like to change from being a senior programmer to being a technical director.

It's variable. Some people rise faster than others for a variety of reasons including a natural aptitude for organization and management, superior communication skills, and being better at schmoozing.

Quote: 5. I'm going to a Computer Science major in college. How will I learn to apply this in game development? Do jobs generally offer on spot training?

You'll need to learn the basics on your own. You won't get hired on the basis of your CS degree, so get to work learning how to make games and putting together a portfolio now. You will get continuing education once you're hired - provided the studio can afford it, of course - but to get up and running it's up to you.

Quote: I have a real passion with programming and gaming, so I'm hoping to become a Technical Director at the end, and really become involved in the game making progress.

Good for you, but you better keep your eyes on the goal immediately in front of you, not the dream position at the end.

Learning the basics on your own,hmm. Does that have to with making mods, etc? Or what?

Quote: Original post by Phunin
Learning the basics on your own,hmm. Does that have to with making mods, etc? Or what?

It means making anything and learning how to do it.

I meant in terms of building a portfolio

The whole reason portfolios are generally considered "a good thing for companies to look at" is that it would be very difficult to make a nice one without actually being skilled. Concentrate on building your skills first. A portfolio comes later, and it generally comes naturally. Mods are one useful path towards game design, and some can be useful for game programming as well.