← Back to context Comment by iopq 11 years ago So what's stopping them from running git blame? 8 comments iopq Reply rbanffy 11 years ago Interviewer time is expensive and candidate time is cheap. bphogan 11 years ago Running git blame is faster than waiting 30 minutes for the results of a whiteboard test. rbanffy 11 years ago Running, then cleaning and then having a dataset that still needs interpretation.I'd take the 30 minute interview route and risk not hiring a clever programmer. 5 replies →
rbanffy 11 years ago Interviewer time is expensive and candidate time is cheap. bphogan 11 years ago Running git blame is faster than waiting 30 minutes for the results of a whiteboard test. rbanffy 11 years ago Running, then cleaning and then having a dataset that still needs interpretation.I'd take the 30 minute interview route and risk not hiring a clever programmer. 5 replies →
bphogan 11 years ago Running git blame is faster than waiting 30 minutes for the results of a whiteboard test. rbanffy 11 years ago Running, then cleaning and then having a dataset that still needs interpretation.I'd take the 30 minute interview route and risk not hiring a clever programmer. 5 replies →
rbanffy 11 years ago Running, then cleaning and then having a dataset that still needs interpretation.I'd take the 30 minute interview route and risk not hiring a clever programmer. 5 replies →
Interviewer time is expensive and candidate time is cheap.
Running git blame is faster than waiting 30 minutes for the results of a whiteboard test.
Running, then cleaning and then having a dataset that still needs interpretation.
I'd take the 30 minute interview route and risk not hiring a clever programmer.
5 replies →