And quite honestly. It shows in the CS grad population too. A lot of us are condescending toward anything that doesn't make sense to us. But, I digress.
The best engineers I've worked with are all non traditional backgrounds, non degree or degree holders from non elite schools. They think differently, they tinker, they are incredibly nice and patient, and do it for the love of connecting humans to technology.
Look up the names mentioned in the article. Garcia, Ranade, Nelson. All of them are involved with highly theoretical mathematics and scientific computing. Just because you're good at 1 thing does not mean you are qualified to teach. And none of these professors are trained or taught or graded or performance managed on how they teach. For most of them, its just required that they spend 10% of their time in the classroom lecturing.
Let's be honest about another thing. 99% of EECS graduates, even from elite schools, are wrangling objects and their relationships to a graph. Simply put, we're all just a bunch of glorified JSON massage therapists. It just so happens that we get paid well for it, and we hold that over people. The same happens in the classroom.
I think in order to facilitate a healthy, educational environment for young adults, we as adults must encourage, motivate and make that environment fun and practical. We force feed binary trees and the compiler AST's, but we need to make it fun. It's like the commonly accepted saying: Schools kill creativity :(.
Worse, a decent chunk of research profs will treat teaching as a burden that just has to be done - a distraction from their exciting world-changing research. So, you get attitudes like the ones you mentioned.
I'm actually not sure why the system is set up to assume that profs who are good at research are automatically suited to teach classes, but that is how it's setup.
I don't think instruction would've changed drastically in the last year though.
I got all that stuff. I've wired up a 4-bit adder on a solderless breadboard for an architecture class. I used to have a well-thumbed copy of Knuth handy. I've designed and built a switching power supply. But I'm not up to date on using Claude Code, and should be.
Start the kids off with high level stuff, but make them do some embedded systems on their way through. At least for an engineering degree. Also, do a bit of lower level communications somewhere in there; expose them to tcpdump/ wireshark, but they need not develop expertise.
Of course, if a student just breezes through it then I would agree. That would make no sense.
+10000. The goddamn slides. If I were a student now going to engineering school, I'd basically take the slides and throw them into NotebookLM and get way better lectures. Then I'd ask claude or GPT all my hard questions. Hell, I'd get the PDF version of my textbooks and do the same.
The number of lectures actually worthy of your time was so low.