Is some of this a failure to distinguish between software engineering and computer science? Some famous CS person quipped that "CS is no more about computers than astronomy is about telescopes." That's fine for studying applied information theory and whatnot, but it seems like maybe the time has come for a formal bifurcation of the fields.

Aren’t the fields already bifurcated? Software engineering degrees exist. The fact that many software engineers have a more theoretical degree in computer science isn’t that unusual; you see the same pattern with business and economics.

Computer science needs renaming - like you said, computer science is not about computers, and it's obviously not about science either (it's closer to maths).

For me it's that 85% of the time I use networking, you're using something that I learned by myself. But that 85% accounts for only 10-15% of the knowledge. So there are a lot of concepts that I learned in school (like DNS, link/physical layer, microarchitecture, etc) that I rarely use. But just because I don't use a lot of the stuff often doesn't mean I never use it. And even the things that I really never use (like programming an FPGA) aren't things that I regret learning.

Any good concurrency resources you recommend?