Based on the OP’s comments and word choice, it seems like the OP needs to work on his communication if he wants to work effectively with the junior dev. Have y

Based on the OP’s comments and word choice, it seems like the OP needs to work on his communication if he wants to work effectively with the junior dev. Have you directly told and then shown the junior dev that reading documentation might make implementing a 2-line code change easier or quicker than watching a video? Do you want to know what a library function returns for your own benefit? If so, look it up yourself. Why ask the junior dev? As a senior dev, if the point of asking what a library function returns is to help the junior dev grow, why not just explicitly tell them what they need to look for (different outputs, errors being raised), explain why those things are important, and then show them how to find/use those things? Maybe the junior dev seems sad because you just randomly send them a link without providing any guidance in how to parse it? Maybe they seem sad because you’re communicating to them in ways that show to them that you doubt their abilities. You said that you have a strong bias towards reading and the junior dev has the opposite. But you said that the junior dev does read in the previous paragraph. Hmm. Can you imagine this same post being written from the junior dev’s point of view?