<p>is CS to EE masters a good route?</p>
<p>I hear EE to CS frequently.</p>
<p>For people young, CS seems like a good major , but when you get older,
it feels like there are more opportunity for EE.</p>
<p>is CS to EE masters a good route?</p>
<p>I hear EE to CS frequently.</p>
<p>For people young, CS seems like a good major , but when you get older,
it feels like there are more opportunity for EE.</p>
<p>EE to CS would be doable. You may have to take a couple of programming classes before jumping into the master though, depending on what electives you took during your undergrad. However, CS to EE masters would be VERY difficult. There would be a large amount of ground to make up because at many schools a CS undergrad doesn’t even require fundamental courses such as Calc III, Diff Eq, Circuits, the list goes on. I’m sure both can be done but the latter would be an uphill battle.</p>
<p>
</p>
<p>I think, no.
EE undergraduate to CS masters is a much better option.
CS->CS and EE->EE are the best options.</p>
<p>And keep in mind, if you are going from CS undergrad to EE with a focus on microwaves, RF, analog IC design it may be a very difficult transition. But if your EE courses will be in embedded systems or computer architecture, then it will be a relatively easy transition.</p>
<p>The only transition that will be easy is one that is at the interface of both fields (like JamesMadison said, embedded systems and computer architecture come to mind). Otherwise, the fields are really too disparate to make such claims. There are topics in CS that would be equally esoteric to an EE as there are the other way around.</p>
<p>Also, I’d like to point out that many CS programs (such as mine) /do/ require a lot of higher level math, especially discrete math. Not to mention that a lot of CS people are math minors/majors as well.</p>
<p>TL;DR - it really depends on which subfields you’re interested.</p>