27 ms·
There is also a goodharts law thing. Coding is more like weight lifting then running. There are some weights that some people just can't pick up. And so if the
by adamgordonbell 3y ago
There is also a goodharts law thing.
Coding is more like weight lifting then running. There are some weights that some people just can't pick up. And so if the job involves lifting things that are usually light but occasionally heavy, then a squat becomes a good measure for candidate.
But once everyone knows a big squat is the way in, they train squats, they show up in lift suits and the whole thing stops being a good measure.
Because on the job you don't squat in a squat rack, but pick things up where they are found, in the conditions on the ground.
Now you have a bunch of people optimized for a task that isn't exactly the job.
- pc86 3y agoAnd then when you try to design an interview process that mimics the conditions on the ground you get people decrying it (sometimes rightly, sometimes wrongly) as too hard, or too long, or whatever.
- red-iron-pine 3y ago"ive been in the industry 15 years, doing this shit is an immediate no!" then you try to get them to explain TCP/IP or fix a for-loop and they're stumped.
- neumann 3y agoSo this. We always give realworld actual mini 'regular day at the office' assignments, and it was a great filter. We ended up giving it a lot because people would ghost or give up after days of (fundamentally bad) work, then the right candidate would arrive and nail it in hours. We had recruiters tell us not to do tech interviews, nobody likes them, etc, but our team was so strong for it. And really, we were mostly testing generics. Use stack overflow by all means, but just know what you are copying and how to modify it!