Thanks Daniel! I definitely like the part on doing code reviews in order to see whether or not your mentee is making progress regarding their goals as opposed to whether or not they are writing good vs. bad code. Sometimes you're in a position though where you're both, a mentor as well as working together on the same project with your mentee, then you're acting in both roles. Then to me at least in the beginning the "focus on your mentee's goals" was the bigger motivation when doing code reviews.
Also one question. What's your experience with people joining your company that are already very experienced but you'd still want to give them the chance to learn. Do you then try to forward those people to other even more experienced co-workers in your company or something like that?
Hi Benjamin, thanks for commenting! I agree that roles get muddy when teams are involved. For example, mentoring tends to be the first thing that's lost when there's time pressure.
I have some experience of bringing in very experienced people. If I think back to those occasions, I think there needs to be a large degree of self-awareness on their part so they can clearly articulate what they want to learn and what their growth areas are. If that can be done, then it's entirely possible for them to learn from less experience co-workers.
For example, teaching is a great way to learn. So an experienced developer can find opportunities to teach a topic to one or more entry-level developers, as a way to learn themselves.
I like how writing blog posts is an advise I am hearing from so many different places lately. Must be something about it ;-)
When I was just trying to think of one particular situation, I am not sure if the topic my college worked on is interesting for people outside of our team but it’s definitely worth having a look.
Thank you!
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.
Thanks Daniel! I definitely like the part on doing code reviews in order to see whether or not your mentee is making progress regarding their goals as opposed to whether or not they are writing good vs. bad code. Sometimes you're in a position though where you're both, a mentor as well as working together on the same project with your mentee, then you're acting in both roles. Then to me at least in the beginning the "focus on your mentee's goals" was the bigger motivation when doing code reviews.
Also one question. What's your experience with people joining your company that are already very experienced but you'd still want to give them the chance to learn. Do you then try to forward those people to other even more experienced co-workers in your company or something like that?
Hi Benjamin, thanks for commenting! I agree that roles get muddy when teams are involved. For example, mentoring tends to be the first thing that's lost when there's time pressure.
I have some experience of bringing in very experienced people. If I think back to those occasions, I think there needs to be a large degree of self-awareness on their part so they can clearly articulate what they want to learn and what their growth areas are. If that can be done, then it's entirely possible for them to learn from less experience co-workers.
For example, teaching is a great way to learn. So an experienced developer can find opportunities to teach a topic to one or more entry-level developers, as a way to learn themselves.
What are your thoughts on that?
Haha you‘re right, Daniel!
I like how writing blog posts is an advise I am hearing from so many different places lately. Must be something about it ;-)
When I was just trying to think of one particular situation, I am not sure if the topic my college worked on is interesting for people outside of our team but it’s definitely worth having a look.
Thank you!