Transition from business to game programming [closed]

This is not a direct answer to your question, "How can I transition?" But instead I'd like to recommend you not go down that road or at least be realistic about what it is like. To back that up I'll quote some stats from the 2004 igda survey on quality of life for game developers:

• 34.3% of developers expect to leave the industry within 5 years, and 51.2% within 10 years.
• Only 3.4% said that their coworkers averaged 10 or more years of experience.
• Crunch time is omnipresent, during which respondents work 65 to 80 hours a week (35.2%). The average crunch work week exceeds 80 hours (13%). Overtime is often uncompensated (46.8%).
• 44% of developers claim they could use more people or special skills on their projects.
• Spouses are likely to respond that "You work too much..." (61.5%); "You are always stressed out." (43.5%); "You don't make enough money." (35.6%).
• Contrary to expectations, more people said that games were only one of many career options for them (34%) than said games were their only choice (32%).

Many years ago I created a couple of game development websites on my own and then was one of the founders of GameDev.net. One of the reasons I did it was to make contacts and get into game development professionally. It definitely worked, a couple of the people who were co-founders have gone on to work in the industry and I'm sure I could have gone that way too but everything I learned about the industry taught me the following things:

• There is an endless supply of developers out there who believe game development would be really cool. The people hiring for the industry know this and aren't going to pay you nearly as well because they rely on this basically inexhaustible pool of people.
• Many of the developers within the industry may be good with 3D or sound or many other topics but often they are inexperienced with basic software practices that you or I might consider essential. In that category I would put things like source control, test first design, design patterns, etc. Even when they know better the time crunch to get stuff out the door often makes them toss good software practices in a foolish attempt to save time.
• Working on a game for two years can quickly become no different than working on any other program for two years. That is, when you have to dig around in the guts of the program day after day and deal with its bugs and only with that one game it's not going to seem all that fun anymore. In fact, you may find yourself playing other games just to get away from it for a while.
• What says you are going to be working on Half-Life X or one of the few dozen cool games that come out every year anyway? Remember, somebody is out there building the game that goes with the next Will Farrell movie and it's probably going to be you. Look around at most of the dreck that comes out. That stuff doesn't develop itself.