I don't think instruction would've changed drastically in the last year though.
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 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.