On Fri, 21 Sep 2007 15:40:24 +0200, Frans Bouma <[EMAIL PROTECTED]> wrote:
>> Well, if it's for a junior programmer they might not have a lot of design >> experience, so asking them to solve a coding problem working it out in front >> of you, and thinking out loud, will reveal a lot about how they think. So I >> wouldn't call this "stupid" (in fact I think that's uncalled for). > > The tests are IMHO stupid because they: >1) could make you not pick the one you should because the daily work the hire >will do is different than writing little routines which are already in the >framework does the question get harder if a method doesn't exist in the framework? (your example was in fact *not* an example or reversing a string in place) >2) could make you pick the wrong person because you think his string reversal >goo was excellent while he'll fail miserably designing some classes or writing >some basic OO code. > the point is if he *cannot* write the function......if he cannot reverse a simple string then what does that tell us? Again it would seem to be the claim there is no correlation between programming and the application of basic algorithms. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
