Thank you for this post!
Until recently I thought it's best having side projects that do not directly relate to the technology you're working with, in order to be familiar with more technologies.
Lately I'm beginning to think it's also nice to deepen your knowledge about the stack you're working with, in order to have more efficient and better solutions on the daily job.
I wonder - do you have any opinion about this?
Depends on what are your needs I usually try to deepen my knowledge while working on "work" projects. I try to take tasks that are a challenge so I am "forced" to improve. I know that this is not possible all the time. But if you feel the need to improve, and you cannot do it this way side projects are very fine way of doing so.
Thank you for this post!
Until recently I thought it's best having side projects that do not directly relate to the technology you're working with, in order to be familiar with more technologies.
Lately I'm beginning to think it's also nice to deepen your knowledge about the stack you're working with, in order to have more efficient and better solutions on the daily job.
I wonder - do you have any opinion about this?
Hi.
Depends on what are your needs I usually try to deepen my knowledge while working on "work" projects. I try to take tasks that are a challenge so I am "forced" to improve. I know that this is not possible all the time. But if you feel the need to improve, and you cannot do it this way side projects are very fine way of doing so.
Thank you for the insights! :)