Yeah, I recognize this. Especially when I ask colleagues to explain why it doesn't work, what he did to fix the problem so that I can handle similar situations myself next time, and they turn me down: It works now, just go ahead! I get even more frustrated when I have the fifth request from the same person about the same problem, having four times spent great effort in explaining slowly and clearly what he/she is doing wrong, and they just ignore it: Just make it work for me! I write several pointed lists of why and how, but even half a screenful is too much: Why can't you highlight what I should do so I don't have to read these useless explanations?? .. and this comes not from end users, but from professionals, who ought to know the explanation but simply doesn't care to. Spending time on understanding can negatively affect their code lines per day ratio ... But then: I have been teaching courses to customers where I have ended up in situations where I've had to say "Just a few seconds, please - you don't have to worry about these details", and then hurried on to set up the correct configuration, or whatever is required to go on. There may be students insisting that they will know all the advanced details from day one, and try to follow me even though I said they shouldn't be concerned (at this stage) about it, getting crossed when I do not explain the things I am doing. But that's what I told them.
