What comes to mind right away: If you can establish a project you can commit to, your choices on what to learn can be guided by context. Don't learn just to learn (unless you think that way, but it doesn't sound like it).
If you can come up with an interesting project you want to see in the world, you can learn at just the right pace to create the thing. And then once it's "done" you don't need to jump on to something new. You could refine that initial thing if you're still excited by it. You'll learn a lot in this process too.
I really like this answer. I got stuck in well if I want to do this I should learn this but if I want to learn that I should learn this first and on and on only to get all twisted up. Love the site!
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.
That's a good question.
What comes to mind right away: If you can establish a project you can commit to, your choices on what to learn can be guided by context. Don't learn just to learn (unless you think that way, but it doesn't sound like it).
If you can come up with an interesting project you want to see in the world, you can learn at just the right pace to create the thing. And then once it's "done" you don't need to jump on to something new. You could refine that initial thing if you're still excited by it. You'll learn a lot in this process too.
I really like this answer. I got stuck in well if I want to do this I should learn this but if I want to learn that I should learn this first and on and on only to get all twisted up. Love the site!