[aub3bhat]

This is an unbelievably bad advice. People underestimate difficulty in learning core CS & Programming materials after they have learnt it. All the while underestimating difficulty involved in learning Math, Physics and EE. As someone who studied Chemical Engineering and later did an MS in CS and now a PhD. I highly recommend studying CS if you are interested in CS. Barring ECE (not EE) the amount of overlap between even Maths / Physics & CS is minimal.

[hajile]

I understood CS a long time before I understood all the math in EE. CS doesn't start to catch up to engineering in mathematical rigor until you are on the back half of your masters degree. I can teach you missing CS theory about how compilers or algorithms work on the job without too much trouble. I wouldn't dream of teaching you how to do polar coordinate conversion for AC circuit calculations on the job under any circumstances though. 4 years of CS is very easy compared to 4 years of engineering.

Theoretical CS is very important, but also quite academic. 99% of developers won't ever delve into that theory and will instead reach for a library based on that theory. The biggest issue in programming is managing large amounts of information that changes over time. This is not only completely avoided in most courses, it is also close to impossible to teach outside of gaining years of experience because every decision is a tradeoff and it takes time to build up an intuition for such things.