4 ms·
>I tell them to send what they have in after two hours that I'm as interested in seeing the structure and thought process than the final result. While this see
by jmiserez 11y ago
>I tell them to send what they have in after two hours that I'm as interested in seeing the structure and thought process than the final result.
While this seems like a good idea on paper, you know that people are not going to stop after 2 hours unless you force them to (i.e. by doing the assignment on-site).
>get it done in 30 minutes, and intermediate 2 hours and a junior probably not finish.
What kind of exercise could a junior programmer not finish? Give up or produce miserable code sure, but not being able to finish? Do you require some really strange domain-specific knowledge?
PS: The website in your profile doesn't seem to be working.
- dpeck 11y agowell with 3 attempts one went over and kept working until he got a solution (took a while), another stopped at around 2 hours to submit and asked for feedback, 3rd finished in time and is a badass. You've be surprised. Maybe I expect too much, but the assignment is essentially network aware k/v store with a single get command and set command. Extremely poor mans redis and a step up from an echo server but for some people doing anything over a network that isn't HTTP breaks them. Thanks for website, my consulting/blog site that pretty much fell into disrepair after taking architect position at a startup.