4 ms·
I've used this in an interview and was very frustrated. Perhaps it was the fault of the interviewer and the way he framed his questions (they were slightly inv
by monatron 14y ago
I've used this in an interview and was very frustrated.
Perhaps it was the fault of the interviewer and the way he framed his questions (they were slightly involved questions -- "write a command line utility that converts an image file, include unit tests, etc.)? I would often have to write my code in the online editor... (so the interviewer could observe my "style") and then bounce out of the browser, throw it into iPython or sublimetext, run the code, debug in my editor... go back to the browser... write my updated code out... rinse repeat.
Code interviews are a bit nerve racking to begin with -- and interrupting my workflow so jarringly doesn't really help. I prefer when hiring managers have me branch a git repo on git hub, encourage me to commit my changes to a project frequently and discuss my thought process on the commits. I think that process works better for both sides.
- prawks 14y agoI think the problem lies in the interviewer in this case. This tool seems to be a substitute for being in an interview room and having a whiteboard to write code on in front of the interviewer, rather than an IDE with a "record-mode". As such, I think the interview question should be posed as if that were the case. In regards to its effectiveness, I think if you take the above into consideration, this tool works very well as advertised. If I were being interviewed with it I suppose I'd just be thankful it has syntax highlighting. Questions for this should be to discover a person's thinking and problem-solving style, not the correctness of syntax/libraries/etc. Things like writing idiomatic code, etc. are much more appropriate to test for.
- c-oreills 14y agoThis. Any time I've done an online coding test it's been working in vim, testing at the terminal and then dumping my code in at the end.