Thanks. A lot of this is similar to what I encountered/observed, to the point where I thought to check the hiring process too. > For example, you sound extreme

Thanks. A lot of this is similar to what I encountered/observed, to the point where I thought to check the hiring process too. > For example, you sound extremely hands-on for a mentor. I would not do all of their coding for them. Well. I guide them through keywords to look up, so they can find more info about their current issue and then ask them to come back when they need to know more or still have further issues ( I do want to see they put in some effort in finding the issue first, depending on the issue ofc). The problem is after some back and forth. If it takes a relatively long time, I sometimes do the coding for them ( a lot less the last years) and I still think it's a difficult balance. Once you fix their problem with pair programming, I tend to get into an akward situation, where it's expected to do that more from their side, which I don't want to do. To the point of the actual request of : "can you take over my screen" or "can you do it for me". Fyi, that's an example of the current senior situation. I hit the "can you do it for me" feedback loop really fast this time.