I can relate to this. Personally, I'm at the beginning of my career, so I spend most of my time learning about what I use at work. Right now, it's all about React, NodeJS, MongoDB and Javascript stuff.
I would loooooove to learn about machine learning, and Elm and other stuff... So, as you put it, I prioritized the subjects I learn. In the end, I think it's important to realize that you can always catch up on whatever subject you decide to skip for now. In my case, machine learning is not going anywhere I think, so I'll catch up when I need to. And if a subject is not around anymore, well, I can reassure myself that it was not a subject worthy to learn.
For a while I felt like I really want to learn Elm but was having the same issue with not being able to really dive in on account of the issues outlined. In addition to the basic framework you outlined, one thing that helped was taking part in a one day workshop on Elm with @rtfeldman
where I actually got my hands dirty.
I still haven't found the time or need to really get deep into Elm, but now I really feel comfortable sitting on the sideline knowing that it's a bit more than an abstract concept I find interesting. I actually know the syntax, some of the details, some gotchas, the workflow, the core library bundle size, etc. This removes a lot of FOMO, and I feel like it's there when I need it now in a way I couldn't only get by reading about it and hearing some podcasts, etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can relate to this. Personally, I'm at the beginning of my career, so I spend most of my time learning about what I use at work. Right now, it's all about React, NodeJS, MongoDB and Javascript stuff.
I would loooooove to learn about machine learning, and Elm and other stuff... So, as you put it, I prioritized the subjects I learn. In the end, I think it's important to realize that you can always catch up on whatever subject you decide to skip for now. In my case, machine learning is not going anywhere I think, so I'll catch up when I need to. And if a subject is not around anymore, well, I can reassure myself that it was not a subject worthy to learn.
For a while I felt like I really want to learn Elm but was having the same issue with not being able to really dive in on account of the issues outlined. In addition to the basic framework you outlined, one thing that helped was taking part in a one day workshop on Elm with @rtfeldman where I actually got my hands dirty.
I still haven't found the time or need to really get deep into Elm, but now I really feel comfortable sitting on the sideline knowing that it's a bit more than an abstract concept I find interesting. I actually know the syntax, some of the details, some gotchas, the workflow, the core library bundle size, etc. This removes a lot of FOMO, and I feel like it's there when I need it now in a way I couldn't only get by reading about it and hearing some podcasts, etc.