3 ms·
That's really his one question he'd ask to someone working in R&D, and writing code? How about asking somebody about the problem domain he'll be addressing? Pa
by pieter 17y ago
That's really his one question he'd ask to someone working in R&D, and writing code?
How about asking somebody about the problem domain he'll be addressing? Past experiences on that field, or related fields?
Recognising bad code might be nice, but I'd pick someone with 20 years of real and relevant experience over someone just new that can say "whoa, that looks like bad code!"
- rdr 17y agocompletely agree, I don't see why this post is specific to R&D ... seems like it's a useful question to ask of any candidate who has to write code, but the essence of R&D seems to be knowledge of the research literature and ability to advance the company's interests through performing innovative research, which this question doesn't at all cover