3 ms·
I like how the article suggests letting applicants bring their own laptops (and only using the interviewer's laptop as a fallback.) Many people don't realize t
by jaredsohn 13y ago
I like how the article suggests letting applicants bring their own laptops (and only using the interviewer's laptop as a fallback.) Many people don't realize that is pretty hard to work on someone else's computer, especially in a stressful situation. (Different installed software, software configuration, keyboard, etc.)
- invalidOrTaken 13y agoI had a remote interview this morning using etherpad, and I was surprised how hard it was without emacs bindings. You'd think that because not everywhere has them (like, say, this HN comment box) it would be easy, but apparently when I'm typing code I really feel it. It really is the little things.
- jbeja 13y agoAgree, on my first ever interview i didn't bring my laptop and the interviewer let me use his, it was so hard because he has Windows in it and i am used to Linux, the editor was Sublime Text and i am use to my own configured Emacs, he was using a GUI tool to create the database when i am use to the command-line for such tasks, at the end that make the interview a lot harder to pass.
- csixty4 13y agoLast time I was involved in in-person interviewing, we told people to bring a laptop with whatever software they were most comfortable using for development. Or, we could provide a freshly-formatted Windows XP system they could install things on if they didn't have something they could bring. Worked out pretty nicely, and definitely made people more comfortable.