Conversation

Notices

1. clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛 (clacke@libranet.de)'s status on Thursday, 18-Jul-2019 01:07:27 EDT clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛
   @Jason_Dodd If I interview for a place and they don't even do smoke testing of my coding abilities, I will wonder what kind of colleagues I will end up with. Even better if it's an excerpt from actual production code, so I'll know what I'll be working with.
   
   People manage to get through the whole interview process, and then you put them in front of an editor and you wonder how they ever got into the places on their resumes ... but probably the same way they got into your place.
   
   The point is not to mouhaha fail the applicant, it's to talk about actual code beyond "I participated in creating a foobar from scratch in blah language".
   1. Jason_Dodd (jasondodd@mastodon.social)'s status on Thursday, 18-Jul-2019 01:20:11 EDT Jason_Dodd

      in reply to

      @clacke I find it interesting, you haven't had questions in interviews that suss that out.

      Actually, when I'm talking to someone about how to code something or solve a problem my go to technique is to discuss it first without a computer being available. I'm most concerned about how someone understands a thing between the ears.