1. First I read some theoretical info about the new technology that I want to learn. It can be a book, documentation, or the information can be in a form of a podcast or a video. You need some theoretical background in order to understand the core concepts.
2. Then from my ideas list I pick a new project to work on. I then create some sketches, designs and start coding. As a new school coder, I mostly use google for answers regarding syntax, methods, patterns and general best practices.
Sometimes it works the other way around: I first decide on the project I want to create, and then learn the tech that the project requires.
I also closely watch the general tech ecosystem, and pick projects that allow me to learn new things, building upon the previous knowledge. In 2019 this will be less important, because now I have my skillset in place, so the main criteria for picking projects will be the project's potential for commercial success.
1. First I read some theoretical info about the new technology that I want to learn. It can be a book, documentation, or the information can be in a form of a podcast or a video. You need some theoretical background in order to understand the core concepts.
2. Then from my ideas list I pick a new project to work on. I then create some sketches, designs and start coding. As a new school coder, I mostly use google for answers regarding syntax, methods, patterns and general best practices.
Sometimes it works the other way around: I first decide on the project I want to create, and then learn the tech that the project requires.
I also closely watch the general tech ecosystem, and pick projects that allow me to learn new things, building upon the previous knowledge. In 2019 this will be less important, because now I have my skillset in place, so the main criteria for picking projects will be the project's potential for commercial success.