It seems that the expierence is not that useful and easy to get.
Is the experience important to older game programmer?
What is the most important thing to a game programmer to get improved?
Tell me more
×
Game Development Stack Exchange is a question and answer site for
professional and independent game developers. It's 100% free, no registration required.
|
closed as not constructive by Byte56, Sean Middleditch, bummzack, Josh Petrie, Tetrad♦ Feb 26 at 3:58
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
It's simple to get out of the industry. Just quit your job. "Experience" on its own is not useful, if "experience" is measured by number of days spent sitting in a chair in a game development office. That is easy to get. What is harder to get are the skills that are required to make games, and harder yet the skills to make great games. Experience is important to the older programmer so that they can justify their salaries. Given the above, though, it is not what people should be focused on. The most important thing that a game developer could stand to improve is their ability to communicate effectively. As an industry, we have few who are truly skilled communicators, and effective communication can act as a substantial force multiplier. |
|||
|
|
|
I've been in and out of games as a programmer, and it has never been a problem. It is more about skills than anything. If you're paranoid, and assuming you're a C/C++ type of programmer, I'd recommend web server tech as something that should mesh well. Distributed computing is very hot these days. Mobile phones require a good understanding of the kind of stuff game programmers do as well, so that's something you could play around with in your spare time as well. |
|||
|
|
|
If you take the "game" out of game programmer, you're still a programmer. You should still have the same fundamental skills as any other programmer (design, testing, planning, communicating, etc.). For example, a game programmer becoming an accounting programmer: the only difference is what you "specialized" in. But given a little bit of time you can easily pick those things up and become familiar with them (like anything else). It'll be even more easier so if your "core" skills are practiced and honed. The reverse path should be equally true. If I understand what my code is doing, how to practice good design and patterns, and communicate well to my team members, then "game" programming is just learning the specializations of that field. Get your foot in the door with an internship and prove that you are a good programmer and are capable of learning the specializations required for your field. |
|||
|
|
|
Programmer makes programs. But business model is a different story from industry to industry. |
|||||
|
