>>12121190>>12120682Two big things about CS. First is that CS could cover just about anything. It SHOULD cover things like networking, datastructures, functional/OOP programming and programming practices, etc. But I've seen everything from "here is how to work in IT" to "webdevelopment 101". The big thing is "do you actually try to learn the material or just try to pass the class?"
I did CS, and a lot of my colleagues were fucking idiots. It's easy to pass CS classes without really trying to know your shit or program much. Meanwhile, I (and a few others) applied ourselves and coded shit for fun on the side. Easy degree, good insight into a hobby then job. If you do nothing but the bare minimum classwork, you probably deserve to fail interviews.
If you can't open up an IDE/language right now and do something simple like "write a function that does X then call it/apply it" (Fizzbang, for example, is the meme one you should be able to bangout pretty easily) then you don't know shit.
I agree that the biggest thing you can do is hobby projects.
I worked in boston for a bit, and the MIT people were great, because it was an entire community of hobby programmers who took classes on the side for the degree. Meanwhile at my college it was a lot of "I need a degree and this one I heard was gud to have" and half of them do the bare-minumum.
I'm of the opinion that if you don't enjoy/want to do coding for projects for fun, then CS probably isn't for you.
College is self-teaching with structure and guidance put in place by people who know their shit. That's invaluable. I hate the idiots who blame teachers for not teaching them stuff, when its quite obvious they didn't even try, and want teachers to be some sort of "Its YOUR job to make sure I know everything despite me not putting in effort". Those people don't get anywhere in life.
