Indeed. When I was interviewing candidates, one of my goals was to get the candidate to respond along the lines of "I don't know.", to which I would follow up w

Indeed. When I was interviewing candidates, one of my goals was to get the candidate to respond along the lines of "I don't know.", to which I would follow up with, how would you find out? No engineer knows everything. I also don't want a candidate that is going to try and bullshit me. Admit to me you don't know, but then tell me how you would rectify that. Google SO, MSDN, man pages, whatever, I don't care so long as you can admit you don't know and have an idea about how to correct that. Personally, I'm doing mostly Python & C++ development at my new job (4 months in) after not using either for 2 years plus. I'm mostly fine with syntax for both, but constantly have my browser open for documentation, mostly for library related info.