I'm definitely guilty of trying to learn multiple things or working on multiple projects at the same time. Focusing on a single thing/problem definitely does help make progress faster.
Went from python baby steps to js baby steps. That webpack, npm, node versions, eslint setup, formater, basic unit tests, asynchronus code it was just blind skiing in forest trying to not hit a tree or moose.
Unless it's about Javascript framework...in that case you need to know about node, webpack, npm (still node, but more specific), and then your framework like Angular or React (so maybe TypeScript too !), and maybe RxJs too, and the librairies you'll use like ChartJs, Moment, Lodash...
Okay, i'm just kidding but I think learning 2 different things that are linked together can be more useful and relevant that mastering one, then the other :)
True, I tried learn webpack before angular and wasn't able to figure out why I would need to use some of its tools. But after I have played around with angular I was able to understand more precisely how could I use it properly.
"but I think learning 2 different things that are linked together can be more useful and relevant that mastering one... " yeah......i totally agree this. Learning two things which are related, has helped me a lot. The thing which I could not understand from one, learning same thing from another related thing helped me to learn that thing easily.
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.
6 . Learn one thing at a time. Don't try to learn 2-3 different things at the same time.
I would say "focus on the problem in front of you". You might need to learn 20 things to solve that problem.
This is a good one!
I'm definitely guilty of trying to learn multiple things or working on multiple projects at the same time. Focusing on a single thing/problem definitely does help make progress faster.
I have learnt this lesson too late.
Went from python baby steps to js baby steps. That webpack, npm, node versions, eslint setup, formater, basic unit tests, asynchronus code it was just blind skiing in forest trying to not hit a tree or moose.
Unless it's about Javascript framework...in that case you need to know about node, webpack, npm (still node, but more specific), and then your framework like Angular or React (so maybe TypeScript too !), and maybe RxJs too, and the librairies you'll use like ChartJs, Moment, Lodash...
Okay, i'm just kidding but I think learning 2 different things that are linked together can be more useful and relevant that mastering one, then the other :)
True, I tried learn webpack before angular and wasn't able to figure out why I would need to use some of its tools. But after I have played around with angular I was able to understand more precisely how could I use it properly.
"but I think learning 2 different things that are linked together can be more useful and relevant that mastering one... " yeah......i totally agree this. Learning two things which are related, has helped me a lot. The thing which I could not understand from one, learning same thing from another related thing helped me to learn that thing easily.