The implication in your question is that there are two options - constantly update your skills, or never update your skills.
The better question is "how often should I spend time learning new techniques and technologies?"
The answer to that question depends a bit on the person, but a good baseline is a few hours each month. Less than that, and you might not be making the best choices and creating more work for yourself later. More than that is fine, up to a point. You don't want to be spending more time learning new technology than you are solving problems for your employer. The caveat to that is if you're a new hire in your first 90 or so days; then, learning is all you should be expected to be doing.
On a similar note, I find it easier connecting with key engineering events happening across the world. I'm always on the lookout from: community.lohika.com/home/events
Some comments have been hidden by the post's author - find out more
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're asking the wrong question.
The implication in your question is that there are two options - constantly update your skills, or never update your skills.
The better question is "how often should I spend time learning new techniques and technologies?"
The answer to that question depends a bit on the person, but a good baseline is a few hours each month. Less than that, and you might not be making the best choices and creating more work for yourself later. More than that is fine, up to a point. You don't want to be spending more time learning new technology than you are solving problems for your employer. The caveat to that is if you're a new hire in your first 90 or so days; then, learning is all you should be expected to be doing.
Thanks, so spot on!
On a similar note, I find it easier connecting with key engineering events happening across the world. I'm always on the lookout from: community.lohika.com/home/events