I disagree. Beyond the idea of sorting algorithm, what this shows is the inability to think algorithmically. A good programmer is not someone who is only able to assemble pieces of libraries together.
No? Hmm. Well, I'm a terrible programmer: I loathe using other people's libraries, I suffer a terminal case of NIH, and in general it takes me forever to get a project released, because I refuse to launch it until every last detail is perfect (and I often burn out on it before I'm done perfecting all those details).
But, I could ace this interview. Hell, I independently developed sorting networks back in about 2002. Present me with a problem and I can probably roll out a pretty good algorithm for solving it, on the spot.
But no startup should ever want to hire me. I'd sink them single-handedly.
So I really don't think that sorting algorithms is the right kind of question for a startup to be asking its candidates.
Comments
I disagree. Beyond the idea of sorting algorithm, what this shows is the inability to think algorithmically. A good programmer is not someone who is only able to assemble pieces of libraries together.
No? Hmm. Well, I'm a terrible programmer: I loathe using other people's libraries, I suffer a terminal case of NIH, and in general it takes me forever to get a project released, because I refuse to launch it until every last detail is perfect (and I often burn out on it before I'm done perfecting all those details).
But, I could ace this interview. Hell, I independently developed sorting networks back in about 2002. Present me with a problem and I can probably roll out a pretty good algorithm for solving it, on the spot.
But no startup should ever want to hire me. I'd sink them single-handedly.
So I really don't think that sorting algorithms is the right kind of question for a startup to be asking its candidates.
"good programmer != only able to glue libraries together" != "good programmer == not able to glue libraries together"