My conclusion from your story is that you needed to cut your losses earlier.
Put them in a situation where they need to produce a result, give them support, but if they need hand holding give them that feedback: you need to be independent on this or you will not be retained.
It sucks, but one or two experiences writing code for a junior dev and then seeing they do not even move on from there was enough. You can have the same kind of issues with crappy “senior” colleagues too, though…
Of course, if you don’t have the right kind of task for an “advanced beginner” (so to speak), that is a problem on the management end.
Bringing up junior colleagues is a fraught business, but when it succeeds you get a LOT of results out of it.
In the end, I try to keep in mind that it is all about money and time. From an individual project point of view, though, it can be very satisfying.
Put them in a situation where they need to produce a result, give them support, but if they need hand holding give them that feedback: you need to be independent on this or you will not be retained.
It sucks, but one or two experiences writing code for a junior dev and then seeing they do not even move on from there was enough. You can have the same kind of issues with crappy “senior” colleagues too, though…
Of course, if you don’t have the right kind of task for an “advanced beginner” (so to speak), that is a problem on the management end.
Bringing up junior colleagues is a fraught business, but when it succeeds you get a LOT of results out of it.
In the end, I try to keep in mind that it is all about money and time. From an individual project point of view, though, it can be very satisfying.