Nothing000 said:
So even though you don't use the discrete math at all, do you at least think that learning about it gave you a greater undersanding of the subject of digital electronics?
And where do you work Berkeman?
I suppose it depends on the treatment of the discrete math, and how concrete they get in their examples. At least for the courses that I took, it was all theory, with very little practical application for real world stuff. Certainly others may feel differently.
I work at
www.echelon.com. We were a startup about 16 years ago when I joined, and thankfully now we are public and doing well. As you can tell from our website, we invented LonWorks technology, which is basically a networking technology that is optomized for multidrop monitoring and control applications, as opposed to data transfer applications like point-to-point Ethernet. LonWorks networking technology has become the standard for many applications like building automation, factory automation, and energy monitoring (like with our Networked Energy Services electric meters).
I worked at Bell Labs, HP and on my own as a design consultant before joining Echelon, and over the years I've done lots of different kinds of design work. As I mentioned earlier in the thread, I think that engineers that can mix several EE disciplines have extra value to a company, because they can really tie together multiple parts of a design. Whether it's helping out in the architecture planning, or even just helping out other engineers to get their work done on schedule during crunch time, having skills in multiple practical areas really pays off. When we interview candidates for positions in our R&D Lab, we look for a mix of analog, digital, software and IC design skills. You don't have to be a hotshot in all categories (just a couple), but being able to work in some depth with all the different specialties is a big help to the team.
I picked up a lot of my RF and analog background mostly after I got out of college, and I wish that I'd taken more of those classes in school, as opposed to the digital theory classes. I'd also recommend that you take at least software classes in compilers, OSs, data structures and C++ if you can. You'd be surprised how much software you write, even as a hardware EE. Also, I'd recommend picking up a little extra probability math, and then taking an in-depth communication theory class or two. There is just so much going on in the communication field right now -- understanding the math behind communications is a very important foot in the door at many companies right now, especially some of the ones on the leading edge...
Also try to build practical projects on your own if you can. Maybe make a habit of building a kit project over each semester break, and a couple of them over the summers. Build more complicated projects on your own using microcontrollers as soon as you can, and get comfortable designing and building practical stuff with them. When you build real-world projects, it really helps you to start to understand what is important in designing and building stuff, and helps you to "learn to ask the right questions" of yourself and your teachers. Good luck! -Mike-