Learning to find answers and sift through documentation (or even source code) is a critical skill I see a lot of junior developers lacking.
Most of the time when I help someone I didn't actually have the answer when they asked, but I did know the terminology to use when searching and how to spot a credible answer.
Two tips I didn't see mentioned in the article are rubber duck debugging and typing out your question into StackOverflow and then googling what you typed before posting it.
2 comments
[ 2.8 ms ] story [ 14.2 ms ] threadMost of the time when I help someone I didn't actually have the answer when they asked, but I did know the terminology to use when searching and how to spot a credible answer.
Two tips I didn't see mentioned in the article are rubber duck debugging and typing out your question into StackOverflow and then googling what you typed before posting it.