Any advice for someone going to college in ECE?

[mrpsychotic]

Today was an eventful one for me. I had been accepted to UC Berkeley for the electrical and computer engineering program in their EECS department in the College of Engineeering and today I accepted their offer. I feel like I am at the start of a long journey, and this makes me excited but also a bit nervous. Basically, I am just wondering if anyone has advice that would be helpful to someone in my position at the start of it all.

A few specific questions:

UC Berkeley offers a five year masters program for my degree, and the cost of that extra year is actually cheaper that an undergrad year for out of state students. I have heard statistics that having a masters doesn't significantly increase starting salary, and that it might not be worth it. That being said, I am not in this degree for the money; I have had a strong desire to make things for all of my life and am very interested in electronics and computers. Given the choice, I would want to work on some experimental project at the edge of the ECE field rather than, say, optimizing some general circuit day in and day out. I feel like having a masters would help me to land these types of positions easier. Moreover, even if the masters degree doesn't earn that much more money, I hope that it would atleast be easier to get and/or hold a job during rought economic times. So, what are your opinions? Is what I am thinking remotly correct? What are your thoughts for or against?

At the EECS department at UC Berkeley, they have two programs, obviously EECS but also ECE. Within the ECE program there are even specialized tracks for specific academic focus. The ones that I am interested in are:
"Electronics (Option I)
For students interested in integrated circuits, including fabrication technology, solid state devices, digital and analog circuits analysis and design, VLSI design, and computer-aided design and manufacturing; and for students interested in microelectromechanical systems, electromagnetics, acoustics, optoelectronics, plasmas, cryoelectronics, and antennas and propagation.
Communications, Networks and Systems (Option II)
For students with interests in networks, control, robotics, digital and analog communications, computer networks, signal processing, systems design and optimization, or power systems planning and operation; or for students with an interest in biology or medicine as well as electrical engineering, including biological sensors and signals, signal and image processing, and analysis and modeling of biological systems.
Computer Systems (Option III)
For students interested in machine architecture and logic design, operating systems, database systems, programming systems and languages, or digital devices and circuits."
Obviously, I don't expect anyone to choose which one is the best for me, since that relies on personal opinion. However, in terms of forming an opinion, what are some jobs that would be specific to each track/ what is the job market for each track/ what are the up-and-coming technologies for each option/ any other interesting information?

The above were just two questions I had, but I am looking for any general advice I can get. If you have read this far, thanks and I look forward to hearing your comments.
 

[krapht]

Go into software if you don't have a significant preference for working with hardware. There are way, way more software jobs than hardware. This is just the nature of the beast, what with all the microelectronic factories moving overseas. For all the talk about software outsourcing, at least you can still work in software without working at a factory. Same can't be said for electronics manufacturing. If you do go into electronic hardware design, you better distinguish yourself as an undergraduate with awesome internships and a high GPA.

And software doesn't necessarily mean your comp systems focus. Comm networks and signals is mostly software work too and you'll probably end up working in DC for a defence contractor or a large telecommunications giant if you go that route.

Source - Soon to be graduate MSEE.

[EEVblog]

If you can afford the time, and are that way inclined, do the Masters. It can't hurt, and you can always leave it off your Resume if needed.
For truly experimental and research stuff, the Masters may indeed help you.

IMO:
Option 3, computer system would be boring as bat poo, avoid. But Krapht is right, there are more software jobs than hardware, not that that matters in my view.
The Biology side of Option 2 sounds interesting, and might lead to some interesting work. Lost of jobs in medical electronics.
Likewise the micromechanical/acoustics et.al aspects of Option 1.
There are high paying niche jobs in VLSI design, but IMO, rather boring.

Dave.

[allanw]

I'd imagine you won't be starting on a specific track anytime soon. Take a few classes and you'll see what you like. They're pretty much the three broadest categories of ECE so any of them is perfectly good if that's what you enjoy.

You probably don't need to think about the 5th year Master's until sometime like 3rd year when you're actually able to start taking some more advanced classes. At that point you'll know much more about what you want to do.

[Bored@Work]

I'd say, go for the master if you think you are the right stuff to do it. That is, plan your finances now so the money at least in theory lasts for doing a masters. Also roughly "plan" your personal live, i.e. discuss with your GF what the longer studies mean.

Regarding courses and subjects, I wouldn't worry too much. Not now at the beginning, where a uni like Berkeley will keep you VERY busy with the basics like math and physics. And not later after you have a bachelor or master. In my country around 70% of all engineers work outside the area they actually studied. Just make sure you get a broad education and don't fear to try something new.

[sacherjj]

When I started school in 1994, Computer Engineering was new and I didn't know if it was valid yet.  I decided to go with a BSEE and almost got a minor in CS.  I now do software for a living.  Did as soon as I left college.  However, I love the knowledge I have from the EE education.

When it comes down to it, Engineering (Mechanical, Electrical, Software) is the same job.  Making something happen with a fixed set of tools.  The processes involved readily translate.  All that is different is familiarization with the techniques and tools available and the limitations which you must stay within.

We had many EEs that were on their way to a medical degree.  That is what Option III sounds like to me.  When I was making this same decision, I looked at which would be harder for me to learn on my own.  For me, that was Option I.  Down and dirty electronics.  The basis for all the others.  Option II is a higher abstraction.  And Option III is even higher. 

I didn't realize that I didn't want to do hardware for a career until my Junior year and started loading CS courses.  But college isn't the end all or be all of anything.  All you learn in college is how to learn.  I've forgotten almost all of my hard math and engineering classes.  For most practical EEs, you don't do much Calculus and such, but I know what I would need to refresh to get things done if I did.