3 ms·
"Believe half of what you see, and none of what you hear" - a quote that really applies here. I've seen quite a lot of developers who are good at talking, and b
by czbond 13y ago
"Believe half of what you see, and none of what you hear" - a quote that really applies here. I've seen quite a lot of developers who are good at talking, and being critical to show knowledge - but usually it's a psychological cover for feeling insecure. This is why some developers brag about knowing obscure things, for example. Anyways, my point is - that if you haven't used it in 13 years, it doesn't matter anyways - don't feel insecure. In addition, many of those coding questions are usually created by 'inexperienced developers' who don't know how to gauge talent, so they put together 'obscure, factual' questions.
- amatxn 13y agoThanks, that makes me feel better. I've met developers like that and was even asked a trick question over MySQL and stored procedures years ago. I will continue to learn for the sake of learning which I've always done - not so much for interviews but to learn how to solve problems in different ways.
- adamcw 13y agoAlso, in my personal experience, "I don't know" is a valid answer to those types of questions, as long as it is followed by an explanation of what your methodology would be to fill that gap.
- amatxn 13y agoI'm not afraid of not knowing an answer. If I don't know the answer its just an opportunity to learn. Each interview I've been in has produced topics or technologies I do not know. I research each and every one after the interview.