If you really mentor, then you don't destroy, you also don't tell them how you did it. As a mentor you should be knowledgeable enough and social-skilled enough to figure out who is sitting in front of you. Try to read and understand them. And then, have the experience to figure out how to help them reaching THEIR next step.
So if you raise a child and the child is getting interested in music, you would help it to get some classes, maybe even a cheap guitar right? All with the knowledge it can fade away and that's totally fine.
All you do is guide, make suggestions and "force" them to step a bit out of their comfort zone and give them safety to do so. Encourage them to go their path.
Who says the person you mentor can't be "better" at what you do in much less time? So suggestion over-hours just means you expect they are as slow (or fast) as you in reaching your goals.
Generally, my approach is always to spark an interest. Not in programming but in figuring out how things work. Figuring out how things are connected. Finance, economy, biology etc. down to the programming language you use.
So get people interested in what they could build and do with the knowledge they are about to learn and get better at. Show them how they are connected. EXPECT that they figure out that most time spend in front of a computer or on an open source project might be wasted if they either a) are not as into it or b) figure out the grand scheme of life.
In the end, we forgot what good mentoring looks like, since it came mostly (at least in Europe) from senior people about the age of 60 or older. Those people looked back and figured out that human interaction and love are more valuable than a side project. But they see you struggle and try to help you reach the next step.
In my opinion, most "mentors" in the software engineering field are too young and too bound to their experience and think it's great just because of a few followers on GitHub or twitter.
In my opinion, if we talk about mentoring in a software engineering field, that's not mentoring but a senior developer helping a junior with their skills. Mentoring means guidance and empowerment, and this doesn't need to be in the same field as you are in.
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.
If you really mentor, then you don't destroy, you also don't tell them how you did it. As a mentor you should be knowledgeable enough and social-skilled enough to figure out who is sitting in front of you. Try to read and understand them. And then, have the experience to figure out how to help them reaching THEIR next step.
So if you raise a child and the child is getting interested in music, you would help it to get some classes, maybe even a cheap guitar right? All with the knowledge it can fade away and that's totally fine.
All you do is guide, make suggestions and "force" them to step a bit out of their comfort zone and give them safety to do so. Encourage them to go their path.
Who says the person you mentor can't be "better" at what you do in much less time? So suggestion over-hours just means you expect they are as slow (or fast) as you in reaching your goals.
Generally, my approach is always to spark an interest. Not in programming but in figuring out how things work. Figuring out how things are connected. Finance, economy, biology etc. down to the programming language you use.
So get people interested in what they could build and do with the knowledge they are about to learn and get better at. Show them how they are connected. EXPECT that they figure out that most time spend in front of a computer or on an open source project might be wasted if they either a) are not as into it or b) figure out the grand scheme of life.
In the end, we forgot what good mentoring looks like, since it came mostly (at least in Europe) from senior people about the age of 60 or older. Those people looked back and figured out that human interaction and love are more valuable than a side project. But they see you struggle and try to help you reach the next step.
In my opinion, most "mentors" in the software engineering field are too young and too bound to their experience and think it's great just because of a few followers on GitHub or twitter.
In my opinion, if we talk about mentoring in a software engineering field, that's not mentoring but a senior developer helping a junior with their skills. Mentoring means guidance and empowerment, and this doesn't need to be in the same field as you are in.