If I do say so myself, I thought I was able to convey a good message, so I’m recording it in an article so I don’t forget.
How to Ask Questions for LearningReally not knowing what to do, I repeatedly asked questions to the engineers in the company every time. At that time, I didn’t even know grep existed, and now I think “I can’t believe I applied for an internship in this state.” It seems I was asking “questions that ask for the answer itself,” and I remember being advised that “instead of asking for the answer itself, it’s better to ask for methods to get the answer.”
And the comment that a colleague designer made on Facebook about this article was also very good, so I’d like to quote it.
I think this is saying something really good. Asking someone who knows for the answer might allow you to finish the task at hand quickly, but in the long run it doesn't help you at all, and you end up not knowing what you don't understand. Moreover, asking for the answer itself is like saying "I have no intention of thinking." If there are many answer choices, you're also pushing the cost of thinking onto others.
It’s a basic thing to “think for yourself, and ask people when you don’t understand,” but I think it would be good if you could ask questions with an appropriate balance.
That’s all from the Gemba.