3 ms·
> Basically: Any question that takes 5 seconds to answer with Google is not a good question. Can't argue there. I haven't done a ton of interviewing in my care
by funkah 15y ago
> Basically: Any question that takes 5 seconds to answer with Google is not a good question.
Can't argue there. I haven't done a ton of interviewing in my career so far, but it is important to me to find out how the other person thinks. Being able to cite function names and package identifiers from rote is not important, at all.
- Turing_Machine 15y agoFrom another POV, I would argue that being able to use Google-searchable resources effectively is a very important skill that should be explored more thoroughly in the modern interview process. The examples and code snippets available on the web (e.g., Stack Overflow) can save hours and hours of time (= money), particularly when the official documentation is crappy. Coupled with that, maybe some questions would be in order about how and when you're legally allowed to use the stuff you find using Google (MIT license? GPL? Creative Commons? How do I have to attribute this stuff? Do I have to release the source?).