If you are sure you want to do software, do CS. If you are sure you want to do hardware, do EE. If you’re not sure or think you might want to work at the interface, do CpE. I’d imagine that it’s easier to transfer to CS or to EE from CpE than any other way.</p>
<p>While it’s probably easier to get into software without CS than it is to get into EE without a major in EE, why compete against specialists (well, at the undergraduate level) for the “good” jobs? That being said, I think most software jobs don’t necessarily prefer CS to CpE, per se, but EE might be a harder sell.</p>
<p>The other thing to consider is that the definition of major programs in “EE”, “CompE”, “CS”, “EECS”, and “ECE” can vary somewhat between different schools.</p>
<p>What kind of advice is this? Easy grade? How can you be so sure that NYU-Poly grads are guaranteed with high salary? No offense, but I think you are giving out bad advice. The EE program at CUNY City isn’t very difficult at this stage of my study. But if a hard program can eliminate the bad engineering students, I don’t think that’s a bad idea. After all, your creation may cause someone’s life. There is no second chance in building a bridge. </p>
<p>===
wdaveo:
I think CS or applied mathematics are better route. I don’t see myself coding Facebook app all day either. I would rather be doing something more scientific, more computational and analytical. I am still a CpE student. It is too late for me to even switch to applied mathematics or CS. In fact, I think I did make the right choice because at this stage I am still not sure of my own interest. Like many people, my interests change every few months or so. CpE allows me to learn about CS and EE at the computer level. </p>
<p>But like ucalumnus, please compare the curriculum of EE, CS, and CpE at each school. The definition is different from one school to another. </p>
<p>At this stage I want to learn more about modeling and simulation, as well as data compression.</p>