News for hackers. Stuff that matters.
Re:Take-home vs. whiteboard coding: The problem is bad inter... by rsanek on Friday April 10, 2020 @11:19AM (#22833890)
I 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.
Re:Take-home vs. whiteboard coding: The problem is bad inter... by ProZsolt on Friday April 10, 2020 @04:29PM (#22837031)
My 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.

Re:Take-home vs. whiteboard coding: The problem is bad inter... by rsanek on Friday April 10, 2020 @09:36PM (#22839047)
It 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?
Re:Take-home vs. whiteboard coding: The problem is bad inter... by ProZsolt on Saturday April 11, 2020 @12:02PM (#22842332)
It 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?