>>11764531Both are fine subjects, but CS is much more than software and EE is much more than hardware.
Most people here have been mentioning “CS jobs” to talk about jobs that involve programming, but a CS job is distinct from this because CS itself (as a subject) is academic in nature, so CS these days are relegated to actual research positions.
Anyway, my take on this is that while both fields are kickass, their undergrad education is a different story. EE has ABET, which generally holds it to a decent if somewhat lacking standard. CS on the other hand is all over the place, and ABET accredited CS programs are often worse than the top programs due to how little they ask for. So to put into perspective, every EE degree from an ABET department is decent, CS is oftentimes hard when you make it hard (take all the hard classes, skip out on the bullshit ones, double down on math, maybe even double major) or go to a good school. “Real CS” is a wonderful subject, but you have to go out of your way to study it - there programs have too many shitters with money to teach harder material outside the top 25ish.
Both degrees can get a plethora of jobs (I know two guys who went into hardware design and programming from CS because of their undergrad research and internships in hardware and VLSI experience), but for the reasons above EE generally has more immediately undergrad keep in other jobs in hardware, communication, etc. On the other hand, CS generally has a much easier time going to the hardest software engineering jobs (and here I mean real engineering, like in cryptosystems, avionics interfacing, HPC), and grad CS at the PhD can take you anywhere (but only if you like research and want to work at a real CS job).
Thanks for reading my blogpost.
