> especially low-level stuff like kernels, bits and bytes, and fundemental details of cryptography and security. Not to say anything about the "unknown unknowns" which I certainly have because I never followed a structured path on the subject.
First of all, the unknown unknowns are much worse from the kid who went to school. Wanna know why? Because the autodidact is definitely better equipped to repair a gap. Its ridiculous to think a 4 year degree can teach a gapless understanding of computers-- do you really expect a 22 year old to have a gapless understanding of any field?
The most important thing a CS degree can teach someone is how to learn more, and at least in my experience it dramatically falls short. Never encouraged to read source. Never encouraged to implement an assignment in another language. The message to me and my peers is clear: learn java and go work for Epic or another dead-end enterprise place.
Last semester I did a hackathon and some of the competitors were 4 kids that clearly did nothing outside of class. My group implemented a mobile app and responsive website. We learned NONE of that in any class. They implemented a GUI desktop application in java with eclipse. (It astounds me how many people can come out of my CS program and the only way they know how to compile their projects is via a green button.)
Second of all: your lack of knowledge about low level stuff is entirely on you. You can learn that anywhere. The problem is that 20 year olds, whether they're in uni or not, think that the high level world of rails and Python is more interesting than bits and bytes. I have never formally learned about the specifics of any of the *nix kernels, Unix tools, python arthimetic, C macros, and more. But I do know about them, because it interests me.
First of all, the unknown unknowns are much worse from the kid who went to school. Wanna know why? Because the autodidact is definitely better equipped to repair a gap. Its ridiculous to think a 4 year degree can teach a gapless understanding of computers-- do you really expect a 22 year old to have a gapless understanding of any field?
The most important thing a CS degree can teach someone is how to learn more, and at least in my experience it dramatically falls short. Never encouraged to read source. Never encouraged to implement an assignment in another language. The message to me and my peers is clear: learn java and go work for Epic or another dead-end enterprise place.
Last semester I did a hackathon and some of the competitors were 4 kids that clearly did nothing outside of class. My group implemented a mobile app and responsive website. We learned NONE of that in any class. They implemented a GUI desktop application in java with eclipse. (It astounds me how many people can come out of my CS program and the only way they know how to compile their projects is via a green button.)
Second of all: your lack of knowledge about low level stuff is entirely on you. You can learn that anywhere. The problem is that 20 year olds, whether they're in uni or not, think that the high level world of rails and Python is more interesting than bits and bytes. I have never formally learned about the specifics of any of the *nix kernels, Unix tools, python arthimetic, C macros, and more. But I do know about them, because it interests me.
Maybe it just doesn't interest you.