On 10/20/07, Guillermo Antonio Amaral Bastidas <[EMAIL PROTECTED]> wrote: > OT: When I interview somebody for a development job, I show them some code > that contains a few errors and useless bits of code hidden inside. I ask > them to review the code and e-mail me back with details on how the coding > guideline for the company can be improved ( clearly a trap ).
There's nothing that pisses me off more than a trap. Who'd work for an employer that sets traps for its employees? If you'd just ask me I'd tell you anything you'd want to know. Just ask me. "Traps" are based on assumptions that may not be valid. If youi come right out and ask an honest question, there are no assumptions to foul up things. Besides... once you hire the person are you going to be expecting them to just happen to find things with the code? Or are you going to directly ask them to please find ways of improving this code? -todd -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
