4 ms·
Oh, practical skills, eh? Debugging? Nope. Version control? Nope. Testing? Nope (at least, no class directly about testing---you were on your own to get y
by spc476 8y ago
Oh, practical skills, eh? Debugging? Nope. Version control? Nope. Testing? Nope (at least, no class directly about testing---you were on your own to get your programs working). Multithreading? Nope. ML? Okay, an introductory course in AI involving LISP. Functional programming? Nope. Declarative programming? A bit of SQL and that's it. Design patterns? Nope.
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.
- beambot 8y agoWhich university? Sounds like the course offerings were weak or you selected poorly. (Though early-90s CS programs were different than today -- truly a different era).
- spc476 8y agoIt was a state university. Their stand out program was in ocean engineering (much better than MIT's program), and the computer science department was new when I attended.
- MaxBarraclough 8y agoI'm not sure if that's a function of your particular college, or of the decade. Perhaps both. 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.)