>         Despite what you may have been told, there is a VERY=20
> simple distinction between EE and CE: a CE is mostly a=20
> programmer. While there are CEs out there that do more, MOST=20
> are programmers. I'm not trying to knock them or anything,=20
> the simple fact is almost every CE I know is almost purely=20
> into software. While they DO know a LITTLE about hardware=20
> most don't care about it. OTOH EEs tend to be MUCH more=20
> hardware oriented. Remember though that an EE does=20
> programming as well, in fact often in the same courses as CEs=20
> (at least in lower years).
>=20

I'm a CE (actually a PhD CE, with a EE undergrad) and I would have to
agree with this statement.  The difference between CS and CE is
typically only a few courses.  CEs will get their hands "wet" with
hardware, and CSs do a little more software engineering and theory.  It
is unfotunate that the CE programs do not do more hardware.  EE's, on
the other hand, do not typically do more than the minimal programming
courses (plus assembler).  They don't get into the more advanced
languages and algorithms that CS/CE folks do. =20

>         From what you've said I don't think CE is right for=20
> you, the simple fact that you CARE about the hardware you're=20
> using gives me the feeling that EE would be more appropriate for you.
>=20

The problem is that EE is three things -- communication, digital and
power.  If the original poster is interested in embedded, then they
might not like communication or power.  I know I hated those.

I would suggest talking to the institution and seeing if you can tailor
the program a bit.  They might support it, they might not.

Alex

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu