One caution though; learn how to limit the learning part, it can become a trap. I have often in the past fallen victim to the pitfall of spending too much time researching tooling and not enough time jumping in.
My methods for avoiding this are to have a core set of criteria that is minimalized. It widens the possible tool list and makes it harder to get caught up in minutiae. Then, I have found that actually just spinning up each set of tooling in testing to find real world implementation issues first-hand is a great first-gate narrower.
This is just a particular subset of learning at work though, so in general what I would say is learn how to get better at learning in general. Learning at work and elsewhere will get better if you do.
My methods for avoiding this are to have a core set of criteria that is minimalized. It widens the possible tool list and makes it harder to get caught up in minutiae. Then, I have found that actually just spinning up each set of tooling in testing to find real world implementation issues first-hand is a great first-gate narrower.
This is just a particular subset of learning at work though, so in general what I would say is learn how to get better at learning in general. Learning at work and elsewhere will get better if you do.