I'm not sure whether to think your school had an awful CS program or you went into your classes with the wrong attitude.
There are lots of practical skills that get taught in universities that aren't direct trade knowledge -- you didn't feel like you learned how to learn? Or were exposed to new ideas and parts of the field that you otherwise wouldn't know about?
> A combination of challenging internships and personal curiosity let me to teach myself everything I was taught in school before I was taught it in school.
Which doesn't mean that their CS program wasn't teaching anything worthwhile, just that it didn't have a monopoly on that value. It also doesn't mean that they had the wrong attitude; on the contrary, I think learning out of self-interest is a much better attitude than waiting for that knowledge to be fed to oneself in a classroom.
God forbid you don't even consider that you're wrong. "Wrong attitude" signaling is pathetic.
> There are lots of practical skills that get taught in universities that aren't direct trade knowledge
That's a problem, but it's also hyperbole. I mean, I'm talking to a 1998 CS/EE from Berkeley who couldn't bother to try to repair his own power supply because it has a danger sticker on it. What you learn in University is to be so blind in your lane, that you don't even recognize it. It's the antithesis of learning to learn.
Write a substantive counterpoint, if you want me to consider a differing opinion.
If you aren't interested in doing that, there's little point attacking me for expressing mine.
Out of that list, I think the only thing I hadn't heard about prior to attending college was multithreading [1]. They did cover a lot of theoretical material though. In fact, there were a few professors in the computer science department that despised computers and barely touched the things (personally, I think they were failed math professors).
[1] I attended university in the late 80s/early 90s.
Today, I'd expect any recent CS graduate to have studied most, or perhaps all, of those topics. In my CS degree we covered every one of them.
(Of course, I'm simply mirroring beambot's comment, here.)
Also, all of the BS humanities and other non-pertinent classes were entirely useless, and for many it seemed the curriculum was entirely politically driven; learned very little from these.
This is just nonsense. I would go so far as to say that I never actually learned anything in my undergrad CS classes. A combination of challenging internships and personal curiosity let me to teach myself everything I was taught in school before I was taught it in school. Of course, I only got those internships in the first place because I went to a good school and had connections that I gained by attending that school, but the idea that an otherwise competent developer can't teach themselves CS theory efficiently on their own is totally absurd.
Furthermore, being taught CS fundamentals in a university is far from a good indicator of developer ability. I've interviewed a shocking number of candidates with at least a BS in computer science who were completely unable to complete incredibly simple exercises (think similar in complexity to FizzBuzz). I expect developers to have a strong grasp of the fundamentals, but they also need to be able to actually apply those fundamentals. CS departments are utterly failing in that regard.