←back to thread

157 points tdhttt | 3 comments | | HN request time: 0s | source
Show context
pclmulqdq ◴[] No.45125831[source]
EE encompasses a lot of "engineering that takes hard math" at a professional and research level (similar to "hard CS," just different fields of math), so it is very hard to do as an undergrad, when your background in complex analysis and E&M is weak.

Early classes on circuits in EE will usually take shortcuts using known circuit structures and simplified models. The abstraction underneath the field of analog circuits is extremely leaky, so you often learn to ignore it unless you absolutely need to pay attention.

Hobbyist and undergrad projects thus usually consist of cargo culting combinations of simple circuit building blocks connected to a microcontroller of some kind. A lot of research (not in EE) needs this kind of work, but it's not necessarily glamorous. This is the same as pulling software libraries off the shelf to do software work ("showing my advisor docker"), but the software work gets more credit in modern academia because the skills are rarer and the building blocks are newer.

Plenty of cutting-edge science needs hobbyist-level EE, it's just not work in EE. Actual CS research is largely the same as EE research: very, very heavy on math and very difficult to do without studying a lot. If you compare hard EE research to basic software engineering, it makes sense that you think there's a "wall," but you're ignoring the easy EE and the hard CS.

replies(7): >>45126229 #>>45126357 #>>45126514 #>>45127402 #>>45127675 #>>45128168 #>>45128950 #
carlmr ◴[] No.45126357[source]
>Early classes on circuits in EE will usually take shortcuts using known circuit structures and simplified models.

Might just be me, but I found it all clicked when we started learning the fundamentals underneath these abstractions. For me it was harder in the first classes because it's about memorizing poorly understood concepts, my brain prefers logically deriving complex concepts as a learning method.

replies(2): >>45126439 #>>45126604 #
sevensor ◴[] No.45126604[source]
My biggest criticism of EE pedagogy is that it tends to proceed from abstractions and then derive the whole world. This makes it a bit of a slog for a lot of students. I’d like to see an application-first approach that builds up principles from observed behavior. Like, measure the slip in an induction motor and then work out what’s going on there, instead of deriving motors from Maxwell’s equations.
replies(6): >>45126618 #>>45128273 #>>45128460 #>>45131520 #>>45132296 #>>45143424 #
1. tekla ◴[] No.45128460[source]
Massive waste of time. So much happens in a way that is not intuitive nor easily observable that starting from the math is much better.
replies(2): >>45128847 #>>45129681 #
2. bee_rider ◴[] No.45128847[source]
The blog post describes the problem with this strategy, I think—the author was already pulled over to the CS side because they could just throw together a web app that people could actually interact with, day one.

If you start with easy circuit models, at least the labs can put together something tangible in the first couple semesters, to keep people interested.

And, I mean, a lot of engineering students end up going into sort of technician-y jobs, so keeping the hands-on spark alive has a lot of value, IMO.

3. sevensor ◴[] No.45129681[source]
So set your sights lower? A lot of BS EEs exit the process understanding neither Maxwell’s equations nor which end of a soldering iron to hold. The degree demonstrates that they are good at abstract symbol manipulation, and that’s not nothing, but it’s not very intellectually fulfilling and it filters out a lot of people who could be good engineers.