> College CS courses aren't necessarily designed to be practical; many are more theoretical and not really practical for day-to-day SWE jobs.
This is the mentality that I really dislike about these courses. How exactly do you get to decide if something is just "theoretical" and "not really practical"? Everything in CS was purely theoretical at one point.
It's easy to say "practical means stuff that is used in the industry", but I mean, I've been paid, by corporations, to do Haskell, F#, and even F* briefly, all of which have been described as "academic" languages, and if you want to be able to work on cool and interesting stuff, there's a high likelihood that you're going have to rely on the "theoretical" world.
This is the mentality that I really dislike about these courses. How exactly do you get to decide if something is just "theoretical" and "not really practical"? Everything in CS was purely theoretical at one point.
It's easy to say "practical means stuff that is used in the industry", but I mean, I've been paid, by corporations, to do Haskell, F#, and even F* briefly, all of which have been described as "academic" languages, and if you want to be able to work on cool and interesting stuff, there's a high likelihood that you're going have to rely on the "theoretical" world.