With some people, it's truelly a great experience. I think these people are mostly curious, eager to learn and are probably smarter than me, when I was their age or had their experience ( they pick it up quicker than me, who spend more time understanding those things).
But I've noticed a pattern with others which I have a hard time coping with.
It seems that sometimes, people forget how many times you helped them to create their current solution ( literally taking over and doing pair programming for the hardest parts).
After a while, some people start to think they know all things better, but it perplexes me since I know which questions they sometimes ask, and it's pretty basic things that were questioned.
Most of the time, they still write horrible code and sometimes they don't understand what they are doing ( eg. Trying to explain known things and their problem with the wrong vocabulary ).
After a while of working on repetitive code, it seems the ego gets bigger so that they want to show authority versus others, while they obviously are still beginners.
Additionally, their behavior is becoming ungrateful and helping them because a burden ( eg. unrespectful).
Is that just me or my character? Or has someone observed similar situations?
Any tips, pointers or books on how to handle these situations better?
What struck me each time is how the things you observe are universally centered around people not behaving the way youd want someone to behave given your estimation of their talent and/or experience.
Ex. "They want to show authority even though just beginners" "they are ungrateful and [this makes them a burden to me]"
The mind-reading is also a big warning sign ("some people think they know all things").
I would either A) reflect on whether my mentorship had devolved into an authoritarian need to rank people and enforce behaviors, as well as demand fealty or B) give more specific examples.
As it stands, the general impression is one of navel-gazing and wanting more credit. To be sure, we are all guilty of that.
Don't pair or do programming work for them. Make them figure it out. They need to get frustrated and figure it out or ask you.
Empower the developer.
Him explaining ideas to others is how many people learn. Let him teach his peers.
Juniors write horrible code. Lucky you are not in a code judging contest. What matters is does it run and does it meet your departments guidelines in terms of coding rules / style. If not don't pass the code review until changes are made.
I think you are providing good knowledge but not giving the person time/space to grow into the role.