3 ms·
Of course it excludes people. Some of those excluded are good people. The claim isn't made that it's some perfect process where no stone is left unturned.
by BackBlast 4y ago
Of course it excludes people. Some of those excluded are good people. The claim isn't made that it's some perfect process where no stone is left unturned.
- ctvo 4y agoNo, the claim is it's a better way to hire "Good Engineers", because what's the point of a method that isn't better than the current standard of white boarding, which we know also excludes people, but has also identified "Good Engineers". This is where data would be helpful, and why numerous people have pointed out that bringing code you wrote, IP owned by your previous employer is a no go, and why we've goal post moved instead to bringing in your personal projects.
- BackBlast 4y agoIt's not a goal post move. The article is explicit about the origin being from personally owned code if necessary. > If they don't have code to share for whatever reason, like it is owned by their previous employer or they are fresh out of school with no code to show, pass on them. > You have other code to share? Data would be helpful, but I don't even know how such data would be gathered. Is there a sure-fire method to identify a "Good Engineer" from one who is not? I interview occasionally, been working a long time. The numbers of devs I know that have such code to share is small, and I would put them all in the work-with-again bucket. I'm not sure if I would adopt this method, but I've seen worse filters :)