3 ms·
> just difficult enough to make it unlikely for most candidates to complete everything. How do you judge someone's half-finished work? Do you expect me to writ
by ProZsolt 7y ago
> just difficult enough to make it unlikely for most candidates to complete everything.
How do you judge someone's half-finished work? Do you expect me to write half-finished code on the job?
- rsanek 7y agoI assume they mean there are individually relatively self-contained pieces of functionality in the problem statement. Not completing an additional feature would still leave the rest of the project in a good state. Perhaps if you use a vcs you could even leave WIP code in an unmerged branch.
- ProZsolt 7y agoMy question still stands. How do you evaluate someone's half-finished work? Do you prefer if I finish more features or my already finished code is better quality or better tested? It's just an unnecessary source of stress during the test.
- rsanek 7y agoIt would probably be best if someone was available to answer these kinds of questions for the interviewee when their time period starts. Though I think it could also be interesting to have this be part of the assessment -- how does the candidate trade off between scope / quality when they are given a fixed time period?
- ProZsolt 7y agoIt is as interesting as evaluating them based on how they indent their code. I can do both but if you don't tell me what you prefer how can I choose?