3 ms·
This topic is very interesting to me from a little different perspective. I am a senior member of technical staff at a very large company and often managers wil
by zw123456 10y ago
This topic is very interesting to me from a little different perspective. I am a senior member of technical staff at a very large company and often managers will have me sit in on job interviews with candidates to cover the technical side. Recently, I sat in an interview and I had my list of questions. It was a telephone interview (1st round, not uncommon), I noticed that I could hear subtle typing in the background as the manager asked various questions. When it came time for the technical questions, I could hear a lot more typing. It occurred to me that the candidate was probably googling the answers. After the interview I mentioned it to the manager and she said "so, isn't that how you guys do it anyhow ?". I was a little taken back and have to admit I did not have any response. But, at least for this manager, how good someone is at googling the answers is a legitimate point of evaluation for a prospective candidate. I admit I use google, stackexchange and etc. to find answers, but it is not my primiary source of information and I just don't think it is a substitute for knowledge, is it ? This bothered me very much.
- hackinthebochs 10y ago> but it is not my primiary source of information and I just don't think it is a substitute for knowledge, is it ? I think this is the real problem of the "just google it!" culture in programming. Expertise is devalued, even seen as wasteful. But ultimately you'll never create anything genuinely new if you don't have a strong base of knowledge to work from. Googling the details is great, but you have to have an idea of what to google if you're doing anything beyond the most basic development.