3 ms·
The guy in the live chat said they look negatively on large numbers of submits. I think this is a poor idea for two reasons. 1) This will simply encourage peop
by doctoboggan 15y ago
The guy in the live chat said they look negatively on large numbers of submits. I think this is a poor idea for two reasons.
1) This will simply encourage people to develop offsite and submit when they have working code. On their site they allow recruiters to see what applicants are typing in real time, and pushing people off site will render this function useless.
2) In interpreted languages like python my work flow usually is incremental change and test, so very high numbers of submissions will not be unlikely. I don't think that kind of programming should be discouraged.
There should be a Test button as well as a Submit button. The employee understood my concerns, so hopefully they get that worked out soon.
Another criticism: The problem desctriptions seemed poorly worded to me.
It is a good looking site either way. I'll be keeping my eye on it.
- extension 15y agoThey could also put a live REPL next to the editor and record the interaction with that.
- ForrestN 15y agoThat's really interesting. If there is criteria beyond the solution you produce, they should really list that clearly on the site. If I don't know that and I'm applying, I might be only half-focusing while doing other things and take a long time and maybe not come up with the perfect solution right away. I think this kind of extra testing could be detrimental because it's going to stress people out. Give a hacker a fun challenge and set him to work, he'll probably do it better and faster than if you set him in an empty room with a big timer and people scowling at him.
- Jd 15y agoCodility has a great test feature. You can load test data and see if the output is what you expect it to be.