Hi Pawel, good question. Yes, I have encountered a junior who needed more time to understand.
Generally if the person repeats the same mistakes, that means:
They forgot and couldn't recall the correct way at that time (most likely)
They are purposely repeating the mistake (least likely in my opinion)
For 1, leaving "fix it" improvement comments on their pull requests enough times usually helps the junior understand that there is a standard/quality, or that "this is how it is done". In my experience juniors will remember and understand after 2 or 3 times. (It could take more times.)
For 2, that might be of a conversation with the junior and why they repeat that same "mistake". Perhaps the engineer believes their implementation is the correct way. Then at that time, the more senior developer can explain why or why not, and have a discussion.
In general I would also ask the junior, "What is your learning style?", as one method of learning may not work for another. For example, many like to start a project by writing as many notes as possible and reading through the entire codebase. Other people learn by writing code immediately, using APIs, becoming familiar with the project by trial and error.
I would encourage more senior developers to take time to understand and communicate with juniors. I think that would solve a lot of problems. With patience and reinforcement, junior engineers should understand eventually.
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.
Have you ever encounter junior who really learn slow and repeat mistakes? If yes, how did you deal with that?
Hi Pawel, good question. Yes, I have encountered a junior who needed more time to understand.
Generally if the person repeats the same mistakes, that means:
For 1, leaving "fix it" improvement comments on their pull requests enough times usually helps the junior understand that there is a standard/quality, or that "this is how it is done". In my experience juniors will remember and understand after 2 or 3 times. (It could take more times.)
For 2, that might be of a conversation with the junior and why they repeat that same "mistake". Perhaps the engineer believes their implementation is the correct way. Then at that time, the more senior developer can explain why or why not, and have a discussion.
In general I would also ask the junior, "What is your learning style?", as one method of learning may not work for another. For example, many like to start a project by writing as many notes as possible and reading through the entire codebase. Other people learn by writing code immediately, using APIs, becoming familiar with the project by trial and error.
I would encourage more senior developers to take time to understand and communicate with juniors. I think that would solve a lot of problems. With patience and reinforcement, junior engineers should understand eventually.