Until recently, professional growth and development was something we had to work on ourselves -- we had to find time in our schedules where we could somehow squeeze it in. It didn't work out so well because the junior devs naturally prioritized completing feature tasks before the end of a sprint, and even though there's talk about dedicating Fridays to learning, we rarely ever found time for it because we're still trying to wrap up tasks with deadlines. I can only assume non-junior devs were doing their own reading up and research. But it wasn't, as you described, a collective team effort.
Lately, our lead has taken the initiative to thoroughly go through every task on our sprint and write out plans and code step by step before handing the task to us. The thought and effort is certainly there, but there could be some argument as to why this isn't exactly a fulfilling or efficient use learning or task time.
I've been super fascinated by the feedback I get from other devs on this topic and I intend to slowly introduce these ideas to my team and see what catches. But, yeah, in the meantime, I think that to satisfy my needs with growth and learning, I'll have to do a lot of the learning on my own where and when I can.
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.
Until recently, professional growth and development was something we had to work on ourselves -- we had to find time in our schedules where we could somehow squeeze it in. It didn't work out so well because the junior devs naturally prioritized completing feature tasks before the end of a sprint, and even though there's talk about dedicating Fridays to learning, we rarely ever found time for it because we're still trying to wrap up tasks with deadlines. I can only assume non-junior devs were doing their own reading up and research. But it wasn't, as you described, a collective team effort.
Lately, our lead has taken the initiative to thoroughly go through every task on our sprint and write out plans and code step by step before handing the task to us. The thought and effort is certainly there, but there could be some argument as to why this isn't exactly a fulfilling or efficient use learning or task time.
I've been super fascinated by the feedback I get from other devs on this topic and I intend to slowly introduce these ideas to my team and see what catches. But, yeah, in the meantime, I think that to satisfy my needs with growth and learning, I'll have to do a lot of the learning on my own where and when I can.