Most of the time when someone ask a question answering it isn't very easy. You have to look things up, go through the code, maybe run some test to figure out wh

Most of the time when someone ask a question answering it isn't very easy. You have to look things up, go through the code, maybe run some test to figure out what the solution is. That is how you work with the code and that is what they need to do to work in the code. The problem here is that they expect that answering would be easy for you, but it is not, so you tell them to go figure out themselves since you don't have the time to do all that work for them every time they get "stuck". Since in fact, you yourself are "stuck" like that every day, being "stuck" is a major part of being a software engineer, it never ever goes away and junior engineers often thinks that being "stuck" is bad. It really isn't, that is what your life will be from now on, you just got to learn how to handle being stuck and nobody can really teach you that. Anyway, when you dragged the answer out of those other people you did the work to unstuck yourself. Those people couldn't just have told you the answer from the start since they didn't know until after the long discussion with you, that discussion was the work. Now that you are on the other side you get a lot of "unintelligent" questions, ie questions you can't easily answer, and therefore feel frustrated with these new engineers. It has nothing to do with kindness, its just that the junior engineers needs to understand that finding the answers to these questions is their job and not something that just juniors have to deal with. Example with overly simple question: Junior: How do I center a div in html? Senior: Just look it up on Google. Junior: Why can't you just tell me? Senior: I just told you how to do it, that is what I do every time I need to center a div!