I just keep writing code, glancing at docs when needed and try to spend as much time as possible actively using the thing I'm learning instead of reading about

I just keep writing code, glancing at docs when needed and try to spend as much time as possible actively using the thing I'm learning instead of reading about or getting stuck in "what if" scenarios. In most cases writing as much code as possible (and looking up things as needed) will help you learn things faster than sitting back and reading. A few days ago I wrote a post on what I learned from 7 programming languages over 20 years[0]. It kind of touches on the process of learning and takeaways. I almost always have a project in mind to build when learning something new. Basically I'm not afraid to experiment. I don't think it's a problem to write code and then throw it away, or spend weeks learning how to use something to ultimately throw it away. You almost always learn something you can apply to something else which is really the main takeaway from the post. [0]: https://nickjanetakis.com/blog/it-is-not-a-waste-of-time-to-learn-a-few-languages-or-frameworks https://nickjanetakis.com/blog/it-is-not-a-waste-of-time-to-...