Richard 於 2014-11-12 5:12 寫道:
> [Please do not mail me a copy of your followup]
>
> dr...@furrfu.invalid (Drew Lawson) spake the secret code
> <m3tkgq$19h5$
1...@raid.furrfu.com> thusly:
>
>> IIRC (it's been a year), one of the code examples I was handed when
>> interviewing for the current job had some problems that were expected
>> to be obvious. It is a quick way to screen out the people with
>> over-padded resumes.
>
> Meh. I'm not such a fan of asking people to be a human compiler,
> particularly on paper without a computer under interview conditions.
>
> We have used a piece of code that compiles but has algorithmic errors
> and told people "this code has 7 errors. How many can you identify?".
> It hasn't been a particularly useful predictor, but it does give you
> more information from which to build a picture of the candidate beyond
> their resume.
>
> The best predictor has been to give someone one or more coding problems
> ahead of time and have them work a solution on their own time at their
> own pace.
>
> Even better than that is to pair program with them for a day.
>