3 ms·
TL, DR; Books are your friends. They are already structured for learning, you just have to experiment with the examples, and do Google-fu when you're stuck. Res
by skydhash 4y ago
TL, DR; Books are your friends. They are already structured for learning, you just have to experiment with the examples, and do Google-fu when you're stuck. Resolve to stick with the problem is a personal thing, but you need a lot if you want to be self-taught. Self-discipline was easy because I was genuinely interested about what I was learning.
I did not touch a computer until around 12 years old. And the computer broke soon afterwards. Then my parents bought a laptop for my brother who was going to college, and I experimented with it for a while (no internet access) and this is when I learned about installing Windows XP (significant). Then everything I learned about computers was playing with friends' laptops (they always wanted me to fix something), and my desktop (still no proper internet access). I've started learning about programming from books I've downloaded at a cybercafé, experimenting with things until I hit a stopping point (not understanding things enough or the examples in the books are no longer compatible). I was in high school and I did have the time to play around, but did so without any mentor, because there were none in my vicinity (either online or physical). So, it was curiosity and determination who got me through.
I've studied electronic engineering, and the CS part was nothing much. It did have two courses on programming for learning the basics of C and Java. But I was already far ahead. I did so by downloading many books (internet access was still intermittent, so I could not always google my answers). My method of learning was playing around with the examples of the first part of the book, then I have enough to tackle a real project. The books became a reference for looking how to do stuff. But I did not focus on programming only. I was learning about computer security, Linux administration, network and network programming, system programming, operating system concepts, game design, UI design, database, and a lot of other stuff. The goal was not really learning facts, but to understand. If something is too complex, I switch to another and revisit later. Still no mentor around and YouTube was not really an option because of the low speed of my internet access.
Now I know enough about the practical side of both programming and computer science that I'm moving to the theoretical part (theory of computation, algorithms and programming language theory). Still the same method, still being self-taught, but I now have better internet access, so I have a lot of help from forums and YouTube to guide me. But it's still the same thing for learning languages: follow half of the book, then look for a little project, to learn about the tooling, libraries and stuff. For tools, I just experiment with them and with the manual as the sole help. Then I read books to see what I missed.