You also want to set time limits on how much time are you going to spend learning. In an ideal world, we could have all the time we need to learn everything. But that does not get us anywhere if we don't apply them in practice one way or another. The best advice we can give is YAGNI unless you really need it.
PS:
Read the relevant section about how Mature Engineers Have Learned How To Learn
That's right. I write that "It gives me the most value when I apply the knowledge to some real-life project or create some sort of snippet with it (a way of avoiding "dry" learning)".
Actually everything I learnt during this process was used in some kind of project/script/workflow. I try to prioritize the "just in time" over "just in case" learning :)
According to the timeboxing part - for me it's +- 30 min each day. Thank you for mentioning that :)
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.
You also want to set time limits on how much time are you going to spend learning. In an ideal world, we could have all the time we need to learn everything. But that does not get us anywhere if we don't apply them in practice one way or another. The best advice we can give is YAGNI unless you really need it.
PS:
Read the relevant section about how Mature Engineers Have Learned How To Learn
dev.to/drm317/becoming-a-senior-en...
That's right. I write that "It gives me the most value when I apply the knowledge to some real-life project or create some sort of snippet with it (a way of avoiding "dry" learning)".
Actually everything I learnt during this process was used in some kind of project/script/workflow. I try to prioritize the "just in time" over "just in case" learning :)
According to the timeboxing part - for me it's +- 30 min each day. Thank you for mentioning that :)