2 ms·
I've seen devs that passed a code test and discussion that had this problem. For example, you can interview someone on a good day, when most of their days are b
by greglindahl 10y ago
I've seen devs that passed a code test and discussion that had this problem. For example, you can interview someone on a good day, when most of their days are bad days.
I don't think there's a magic interview style that prevents this problem. Corrective action and fast firing if necessary have worked for me. And whatever you do, don't impose onerous procedures on all of your devs because one of them screws up on a regular basis!
- beekums 10y ago> And whatever you do, don't impose onerous procedures on all of your devs because one of them screws up on a regular basis! This is a really important point. Creating processes for the lowest common denominator just stifles every other developer.
- Karunamon 10y agoSeconded. Sometimes the answer to a mistake being made is not to take on a boatload of process in an attempt to make sure it can't happen again, it's to slap the hands of the offending person and say don't do that.
- rokosbasilisk 10y agoIve never done the interviewing, so Im not sure. But if someone fails their code test or discussion doesnt that suggest they are a higher risk factor for being a "net negative"?
- falsedan 10y agoCorollary: also don't make processes which enforce the habits of your top performers
- deleted 10y ago[deleted]