Well, first there is the egg and chicken problem: a new grad has no significant project to account for, and yet he has to start somewhere (and may well develop into a super-star coder). Second, you want to know what the person is capable of, not what he was given to do by that or another pointy haired boss at a company that happened to be his previous work place. Third, what if you are looking for a back end developer in a massively distributed environment? What good is for you the little app this guy wrote using the AppEngine?
His approach may work in some very specific, well controlled circumstances, but it doesn't scale.
The egg and chicken problem is obvious, I even have figured it out myself. :-) On one hand no one should expect tons of cool software from a graduate, on the other if he hasn't developed anything worth seeing as a part of his study or for fun - it may ring a bell as it may be a sign (not necessarily it is) of lack of interest in profession.
Second is true, yes.
Third argument is just a game of examples. If a guy has developed a tiny little bit of a backend in a massively distributed environment and he can explain what he did, in what way, why it was important and how it could have been done in a different way it is worth the same as if you played it on your Android phone. You won't be able to test his words, but you will find out if he understands what he is talking about.
But truth is of course there could be no standard way which is applicable to literally everyone.
Disclaimer: I don't have my own strong opinion on these matters, I rather like to read, listen and discuss.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2011-05-11 01:03 pm (UTC)(no subject)
Date: 2011-05-11 01:06 pm (UTC)(no subject)
Date: 2011-05-11 01:10 pm (UTC)His approach may work in some very specific, well controlled circumstances, but it doesn't scale.
(no subject)
Date: 2011-05-11 02:23 pm (UTC)Second is true, yes.
Third argument is just a game of examples. If a guy has developed a tiny little bit of a backend in a massively distributed environment and he can explain what he did, in what way, why it was important and how it could have been done in a different way it is worth the same as if you played it on your Android phone. You won't be able to test his words, but you will find out if he understands what he is talking about.
But truth is of course there could be no standard way which is applicable to literally everyone.
Disclaimer: I don't have my own strong opinion on these matters, I rather like to read, listen and discuss.