2 ms·
Don't see the point of these "take home projects". Just ask them what's the most difficult technical thing they had to do before, and have them walk you throug
by laichzeit0 2y ago
Don't see the point of these "take home projects". Just ask them what's the most difficult technical thing they had to do before, and have them walk you through it, probe, ask questions. If you don't like the one they talked about, ask about another one, or another one. You can generally weed out the bullshitters, they talk alot about "we" and hardly ever use "I" meaning they didn't do anything.
- hackable_sand 2y agoI would say "we solved this issue" if all someone did was hand me a coffee while I was debugging. What compels you to play lingual games with peoples' livelihoods?
- laichzeit0 2y agoWell I find conversations with people in interviews to be less of a game than giving them “homework” to do, given that unless they’re totally green with no work experience, I’d assume they would actually have some stuff they’ve worked on and would like to talk about. It’s completely bizarre to me that take home assignments have been normalized as part of an interview with professional working people.
- hackable_sand 2y agoIt's a constant tug of war between standards and expectations. I personally prefer hypotheticals, or some variant on live pair programming. Also, as someone with enough free time to do take-homes, I also prefer code reviews over that one-off code which then becomes a case of 100% "I did this and here's why". Even with that last example I would say, "well to optimize, etc., we could do this".