81–90 of 144 posts
Earlier quoted context omitted.
RC filter is like fizzbuzz for EE.
One of those is a basic building block used in pretty much everything, the other is software bullshit.
Practical Electrical Engineering by Makarov et.al.
Electronic Circuits: Handbook for Design and Application by Tietze, Schenk et.al.
Sensors and Signal Conditioning by Ramon Pallas-Areny et.al.
Introduction to Embedded Systems: Using Microcontrollers and the MSP430 by Jimenez et.al.
Patterns for Time-Triggered Embedded Systems by Michael Pont.
Electrical Engineering 101: Everything You Should Have Learned in School
Why push yourself through a degree-style path? So much of what EEs learn in their coursework is of low utility. (I'm a physicist who transitioned to working as an EE. I have never had a single EE course, and yet I find myself with no obvious deficits compared to my colleagues who have.) There are two ways to learn an existing technical-ish subject: you can spend a lot of time reading textbooks, then do some projects…
As a practicing EE / RF comms engineer, I will say that it is very obvious when you're working with someone who thinks that their EE coursework wasn't useful for the real world.
Earlier quoted context omitted.
One of those is a basic building block used in pretty much everything, the other is software bullshit.
I feel attacked. I'm a DSP engineer and I haven't implemented an analog filter since I graduated. If we got into detail on RC filter gain and phase shift I'd fail. Do I have to give my EE degree back?
Why push yourself through a degree-style path? So much of what EEs learn in their coursework is of low utility. (I'm a physicist who transitioned to working as an EE. I have never had a single EE course, and yet I find myself with no obvious deficits compared to my colleagues who have.) There are two ways to learn an existing technical-ish subject: you can spend a lot of time reading textbooks, then do some projects…
>I have never had a single EE course
Enough said.
I have some recommendations for you as an EE graduate, you can club Digital Circuits and Systems, Embedded Systems and Digital Hardware with one book in one continuous course with the book Digital Design and Computer Architecture by Harris and Harris (A RISC V Edition will release soon in 2-3 months, buy that one) For Electronic circuits choose Microelectronics by Behzad Razavi. Instead of Purcell go for "Engineering…
Yes, it is too broad. You should look at a school like Berkeley and look at their concentrations. Maybe RF isn’t important if you’re doing systems (unless you’re interested in RF). https://m.box.com/shared_item/https%3A%2F%2Fberkeley.box.com...
I used to build BMI systems in graduate school, from the lowest level (mixed-signal analog design for 70 uV extracelleular signals) to DSP (128 DSPs doing real time analysis) to the network (built my own ethernet MAC, foolishly!) to all the vis and RT-linux-based analysis. I left the area and switched into ML in grad school, but if I had to do it all over again there's one thing I think is missing: Optics. Optics opt…
Maxwell would have agreed.
Nicely written. For certain. Would it be cruel to suggest that you might want to advance a bit more before weighng in ? I'd say that semiconductor physics, real math, control systems, real mixed signal and a couple of others should get a go ... but my eldest child didn't get much past this, so maybe the state of the art today? Again- I mean no cruelty in my comments, but seems as if modern curricula are not teaching…
I'm not sure they ever did. They should imho be teaching the ability to learn and adapt to changing and emerging technologies, and to think critically. I'm still using the mathematics I learned in college, to understand things that didn't exist back then such as elliptic curve cryptography.