5 ms·
I tend to say, and this has not worked well for me, "Uh, I would google it, and see what other people have done, and learn from their experiences, and either us
by jerrya 13y ago
I tend to say, and this has not worked well for me, "Uh, I would google it, and see what other people have done, and learn from their experiences, and either use their license appropriate code, and or their knowledge and experience and consider that and how it would fit into our architecture and start from there".
Because that's how I engineer. I try to stand on the shoulders of others. And Google provides such an excellent step-stool.
But as I've said, that doesn't seem to go over well.
Implement your favorite sort algorithm? I don't know that algorithm, I tend to use the sort algorithm that comes along with the libraries of the language I am using on the assumption that a) it's good enough until proven otherwise, b) it's well implemented and mostly bug free by the language designers, and c) schedule is paramount, the most bummed out, tweaked out, sort is not.
- dclowd9901 13y agoYeah, but this differs in what I'm talking about, in that I am going to prove to you that I'm good at doing the most important part of the task: implementing an idea into code. I think, regardless of memorizing a specific algorithm, if I can prove that I can understand something after only knowing about it for a few seconds, and then actually create a mechanism that works with that understanding, that's really what an interviewer would want to see.
- jerrya 13y agoI thought that by telling them I would use google to learn what other people have already learned about the task, I WAS proving to them I know how to implement their ideas into code. I am more worried about the folks that just jump into a complex project without seeing if someone has already done this beforehand.