Dominic998: Regarding HoneyBakedHam's comments, that is true, but I really want to be involved more in the design and making side, rather than on peripheral things </snip>
Game design isn't done by the programmers. Programmers are, sadly, mostly just code monkeys at game development studios. I don't know exactly what you mean by game making, but the game design is usually (depending on the type of game) done by a mix of the following job types:
Writer (look at BioWare for an example of how much pull a writer can have in a story-driven game)
Level designer (often have some programming experience but work with map tools)
Environment artist (similar to above but heavier focus on modeling, programming is very high level - ie scripting)
Project leads (but it's likely very rare to get hired on as one vice climbing the ladder, to so speak)
Coding in general is a tedious job, though it pays off when you get to solve a problem that you couldn't make heads or tails of at first, or when you complete a project that you put a lot of effort into. But don't make the mistake of too many young graduates - most technical jobs in the IT and programming field are very heavily results-biased. If you don't have a portfolio when you graduate, you've screwed yourself badly. Get your bachelor's, but start now on actually writing some programs so you have something substantial to submit when you get past the HR stonewall.
(disclaimer: I work in networking, not programming, and never even had a job that was mostly about programming. My knowledge is from friends and coworkers over 15 years, not personal experience.)