Are you specializing in one particular area or opting for a general degree "knowing a little about everything"? Which do you think is more employable?

For instance, although my university offers "Computer Game Design", I suspect the competition in that area is fierce and non-game employers would probably roll their eyes seeing that.

I'm thinking either a General degree or a Software Engineering concentration would offer more flexibility. I could be wrong...

Most IT jobs that I see are in software development. If you enjoy programming, this would seem to be the best focus. There also seem to be plenty of entry-level programming jobs available.

I am focusing on programming a lot, but dabbling in a little of everything (including web design) I feel you can never know too much and can never be too experienced with all of that.

If you want to be a game developer, just get a good software engineering background. Data structures, calc, physics, algorithms, software engineering, and a demonstrated love of games (including writing some small ones on your own) is what'll get you a game development job, not a specific game design class.

That being said, the game design classes I've seen shouldn't be eye-rolled at by employers. They tend to have team groups work on decent-sized projects, which is a useful skill no matter what area of software development you go into.

I'd go with Software Engineering. It should cover areas that would be useful for game design, but also useful in other areas of development (inc ase you don't get a game job).

I work down the street from Midway here in San Diego, doing programming for a GPS company. When I met up with some of the developers for Midway in San Diego at a nearby deli, I was kind of surprised a couple of them got their start in QA. It's all about networking in the end, though.

I work down the street from Midway here in San Diego, doing programming for a GPS company. When I met up with some of the developers for Midway in San Diego at a nearby deli, I was kind of surprised a couple of them got their start in QA. It's all about networking in the end, though.

QA is a good foot in the door, especially for design or art jobs (although engineers can get a foot in the door by writing automated QA tools, etc).

I graduated BS-CompSci with Majors in Computer Engineering two years ago. It's mostly about microcontroller technology. Went into the software development business though. I currently have a MCP cert., studying my way through MCSD and MCAD certificates, although I'm sometimes grasping at straws when it comes to multi-language programming.

Go with software engineering. It's what I should have just done in the first place. Lol.

My CS degree allowed me two focus areas - the one I didn't do but should have is databases.

QA is a good foot in the door, especially for design or art jobs (although engineers can get a foot in the door by writing automated QA tools, etc).

Yeah, I didn't go into too much detail when I was inquiring about how they got into their actual gigs regarding QA, but I thought it was kind of neat. Maybe one day I'll get into game developing... though, admittedly my C++ / C# skills aren't exactly up to par.

I did software engineering and databases. Can't really go wrong there. Make sure you take at least one group project course.

The only other thing you might consider is network security (a lot of schools don't even offer it exactly), but probably only if you think you'll get a master's fairly soon. Very high demand for those types.

Any specific skill set that people can bring to the job will be technologically obsolete in a couple of years. IMO it's better to hire people that are going to be able to learn any new technology rather than people who happen to know SQL programming right this minute.

Software Engineering, Analysis of Algorithms and things like that will serve you forever.

Edit: With that said, if a course in game design sounds fun... take it.

I was very happy when my school got Web Design, because we have a game design class now which I am going to take. I am pumped.

Here's the tentative plan with a SENG concentration. It seems "well-rounded" with the restrictions in place. Once you choose a concentration, there's not much room for options.

Year Three
-----------
CPSC 349 - Programming Paradigms
CPSC 413 - Design and Analysis of Algorithms I
CPSC 457 - Principles of Operating Systems
CPSC 433 - Artificial Intelligence (option)
SENG 411 - Human and Organizational Aspects in Software Engineering
SENG 443 - Software Architectures

Year Four
----------
CPSC 441 - Computer Communications (option)
CPSC 471 - Data Base Management Systems
CPSC 481 - Human-Computer Interaction I
CPSC 501 - Advanced Programming Techniques
CPSC 565 - Emergent Computing
CPSC 594 - Software Engineering Project

It looks like so little when laid out like that! :)

Any specific skill set that people can bring to the job will be technologically obsolete in a couple of years. IMO it's better to hire people that are going to be able to learn any new technology rather than people who happen to know SQL programming right this minute.

Absolutely agreed. The program I went through was top-notch; heavy focus on learning how to do things in the abstract and moving towards the specific rather than learning Java, Pascal, etc... in the dozen or so courses that involved programming, I think we used seven or eight distinct languages.