Are you thinking of going it on your own, like Cas, or going to work for a game company.
Both are hard and not for the timid. Going it alone is like any small business and the sad fact is that most small business fail in their first 5 years. Make sure you really udnerstand all the issue sof amrketing yoru product and colelctign income before you try it, there’s a lot more to being a successful independant game publisher then just engineering.
If you go to work for a game company as either an employee or a contarctor you can expect all of the following:
Overload of work (60 hr weeks normal, 80-100+ on deadlines).
Frustrating development cycle (publishers liek to see “viewable/playable” milestoens which means you CANNOT gnberally engineer in an efficeint way but must build at least semi-molotihic and code-redundant apps.)
Lousy Pay. (When I was doing it, 85K was a high end alery, just for comparison.)
Little security. (A game project can go south for any numerb fo reasons thata rent your fault. it at least used to be commo npractice at game companies to respond by firing the entire team. Even if you are secure at your company, game companies themselves go out of business all the time.)
Its a dirty, nasty business frankly. The compensations are mostly internal. If you are going to do it, it better be for love.
Sorry to thow cold water, but these are the reasons I got out of game development itself.
If all you want is to do ‘somethign worth while’ you might consider keeping your day job and working on a small game nights/evenings…