3 ms·
I think everyone of those points is dependant on some underlying assumption that its possible to have some snippet of code that makes it possible to evaluate ho
by daleharvey 16y ago
I think everyone of those points is dependant on some underlying assumption that its possible to have some snippet of code that makes it possible to evaluate how good you are as a developer, which at least to me sounds about as crazy as judging develop productivity by lines of code.
- mattm 16y agoI think there is some truth to that. When I am new to an existing codebase, in under an hour of reading code I can gauge the experience level of the coder. Of course, a tiny snippet of code would not be as useful.
- _corbett 16y agoI agree with you there for sure. The more holistic the interview process the better IMO. In fact I'd prefer to see a project in addition to a snippet. You can't tell a decent coder from a great one with a snippet, but you can get a picture of their code and their tastes.
- anthonyb 16y agoIt won't evaluate how good you are, but it's a very easy way to tell if you're bad. Think Fizzbuzz and you'll be on the right track. I've had people who've submitted code which doesn't run, has obvious buffer overflows and bugs, or is just plain indecipherable. You'll also have an ice breaker if you want to interview them - just ask them about their code...