| >Bob: Is there any advice you'd like to give to young programmers/computer science students? >Linus: I'm actually the worst person to ask. I knew I was interested in math and computers since an early age, and I was largely self-taught until university. And everything I did was fairly self-driven. So I don't understand the problems people face when they say "what should I do?" It's not where I came from at all. This is a problem I don't understand too. If you are really into something you motivating yourself in doing things. You can see how stupid people are when you just read the questions on Stackoverflow today. Nobody seems to figure things out by themselves anymore. Same with YouTube, when people explaining simple math things with extremely effort people complaining then that today's teachers are shit. But it's more your own lack if you're not able to imagine these thing inside your mind by yourself. |
That being said, I do think people owe it to themselves to read the documentation first. I’m extremely rarely in a situation where the official documentation isn’t monumentally better than every other option. There are a few exceptions of course, when the official documentation flat out sucks.
I do think we have a general issue with how we teach CS though. Especially outside the hardcore CS degree, because we’re really not teaching young people computation anymore, we’re teaching them how to produce results. This is especially true for places like Udemy and YouTube, but it’s frankly also true on more UX centric or academy/bachelor level degrees.
I do external examinations on academy levels, and earlier this year I went to a place where they teach associate degrees in CS. Only they opted to build their places as a “gaming education”, so they had a heavy emphasis on Unity. And sure enough, the students were pretty good at unity, but only a handful of them knew how to calculate Big O of a few simple examples and only a single student knew how a computer actually works.
When I did my own freshman year, one of my first tests was to decode a hidden message by altering the contents of a bitmap file using C. That’s pretty useless, sure, but it teaches you a lot of things, including how to read the official documentation for a bitmap, which is a much more useful skill than knowing how to use a certain version of some framework. At least in my opinion.