Knowing how to find the answer is an often underestimated trait of successful developers. When I interview someone I often ask them what they will do if I'm ou

Knowing how to find the answer is an often underestimated trait of successful developers. When I interview someone I often ask them what they will do if I'm out-of-the-office, no other senior devs are around, and they need to find the answer to continue to be product - what do you do? You would be surprised how many times I hear 'wait for you to return', versus 'I'd fire up duck-duck-go or search stack overflow'.