A little bit about my motivation and learning methodology.
Unlike most people that start learning to code, I’m not into a career change (at least not for now) and I was not always fascinated by computers, electronics and so on. I would say that for me, coding is more like a hobby driven by curiosity and a need to challenge my intellectual limits.
This is important to mention upfront because it dictates the tempo of my learning curve. I’m in no rush and I don’t have to sacrifice other important aspects in my life (quality time with my family, my full time job, my health or other interests and hobbies). I don’t invest a lot of time in coding but make a slow and steady progress.
I’ve decided to write a blog documenting my learning for two main reasons. The first one is that I believe it would help me learn better by having to explain what I’m learning and doing in my own terms. The second reason is that I don’t think that there are many resources out there that describe the learning process itself as it happens. Most tutorials are made, of course, by people that already know to code. Yet, I doubt that they know HOW did they learn in the first place. Usually, their thinking goes something like this: “In order to build X you need to learn A,B and C”. Today, after spending hundreds of hours learning programming, I can say with confidence that the path is not linear at all. They just forgot how it was in the beginning.
I would say that learning to code has two important aspects: algorithm and syntax. While they are intertwined, with syntax influencing the algorithm choice, I feel that each one has to be learned in a different manner.
<htm> instead of
<html> would make it curse you with an error message, or ignore you altogether.
Also, I try to read many articles about coding – mostly about the languages I’m learning now – and to listen to coding related podcasts (usually when I’m walking the dog). And one more tip, type the code, don’t copy paste it.