I am in academics and so I think that you may benefit from the perspective that the universities are trying to follow.
ACM, IEEE, AIS, etc. have engaged in an exercise to resolve some of these issues from a curriculum clarity perspective. This would be relevant to you since you are going to enter a 4 year program and engage in a formal curriculum. ACM has a master document which is called the CC2005 document which provides a perspective of what the scope of area like CS, IT, EE, CE, and MIS is. There are also reference curriculum that for each of the areas like the IT2005 for IT degree. Given the focus on some kind of standardization and accreditation in most universities, these documents will give you a good reference as to what you will learn in these programs. That may be your starting point since as you go along you can start at one place and end at another easily given your interest, committment, and initiative.
From my personal perspective I would highly recommend a CS or a CE degree which gives you a sound base and understanding of the concepts at the undergraduate level. Building on other knowledge areas like business areas can happen subsequently or if you are interested in a parallel mode with dual majors. Though I teach in MIS my undergraduate degree in Computer Science and Engineering always gives me some advantage everytime I run into situations. The main thing you may want to consider is that how happy are you with a black box approach to things as opposed to knowing how is all really works. There are benefit of each but I have not found many people who will pick up a book later in their careers and learn graph theory, algorithm complexity, NP completeness and so on. I would say that if you have the will learn the stuff that will stay with you for times to come and that means conceptual knowledge, go for either a CE or a CS degree
Slashdot Mirror
If you are in a Windows Environment check out ViceVersa Pro.
I am in academics and so I think that you may benefit from the perspective that the universities are trying to follow. ACM, IEEE, AIS, etc. have engaged in an exercise to resolve some of these issues from a curriculum clarity perspective. This would be relevant to you since you are going to enter a 4 year program and engage in a formal curriculum. ACM has a master document which is called the CC2005 document which provides a perspective of what the scope of area like CS, IT, EE, CE, and MIS is. There are also reference curriculum that for each of the areas like the IT2005 for IT degree. Given the focus on some kind of standardization and accreditation in most universities, these documents will give you a good reference as to what you will learn in these programs. That may be your starting point since as you go along you can start at one place and end at another easily given your interest, committment, and initiative. From my personal perspective I would highly recommend a CS or a CE degree which gives you a sound base and understanding of the concepts at the undergraduate level. Building on other knowledge areas like business areas can happen subsequently or if you are interested in a parallel mode with dual majors. Though I teach in MIS my undergraduate degree in Computer Science and Engineering always gives me some advantage everytime I run into situations. The main thing you may want to consider is that how happy are you with a black box approach to things as opposed to knowing how is all really works. There are benefit of each but I have not found many people who will pick up a book later in their careers and learn graph theory, algorithm complexity, NP completeness and so on. I would say that if you have the will learn the stuff that will stay with you for times to come and that means conceptual knowledge, go for either a CE or a CS degree