This is a pet peeve of mine. I have a couple colleagues that use this too often. It's dismissive and rude, it presents to the questioner the impression that you perceive them as ignorant and stupid.
The fact is, much of software development is really the application of arcane processes, commands and procedures to solve problems. New people don't know your particular process or tool suite. I worked in an office that used Rational Synergy and Doors. When I was new I had no clue how to use these properly. After some experience they became easy, but going to a colleague and being told "that's easy, just X" was rarely helpful, because it turned out that X was actually A, B, C and D. Admittedly, sometimes A and B were just "click on the options menu", "click on the <entry>", but finding C and D required knowing that.
These sorts of things are, in fact, easy, but they're still arcane enough that when you provide an answer it should be a complete answer. Anything less will result in the questioner being unable to complete the task and feeling like an idiot, possibly being too embarrassed to go back and ask a followup because you told them "it's easy". If, instead, you told them "Oh, that's X, you need to do C and D", you've not poisoned them with "just" and "easy". If they don't know how to do C then they can come back to you and you can say, "Oh, you need to do A and B, then C is the third option down in that tab."
The fact is, much of software development is really the application of arcane processes, commands and procedures to solve problems. New people don't know your particular process or tool suite. I worked in an office that used Rational Synergy and Doors. When I was new I had no clue how to use these properly. After some experience they became easy, but going to a colleague and being told "that's easy, just X" was rarely helpful, because it turned out that X was actually A, B, C and D. Admittedly, sometimes A and B were just "click on the options menu", "click on the <entry>", but finding C and D required knowing that.
These sorts of things are, in fact, easy, but they're still arcane enough that when you provide an answer it should be a complete answer. Anything less will result in the questioner being unable to complete the task and feeling like an idiot, possibly being too embarrassed to go back and ask a followup because you told them "it's easy". If, instead, you told them "Oh, that's X, you need to do C and D", you've not poisoned them with "just" and "easy". If they don't know how to do C then they can come back to you and you can say, "Oh, you need to do A and B, then C is the third option down in that tab."