Say you need a bunch of smallish apps written. For the small cost of putting up a job listing on monster )or whatever jobsite of your choice) you get applicants who seem decent enough by resume. Then talk to them for 15-30 minutes and say that the next step of the hiring process is a 4-6 hour programming test. They'll be excited and work their
(
Read more... )
Comments 3
You're also neglecting one some of the biggest expenses with this approach - documentation, integration, test, and maintenance. And you can bet that code written under that type of time and interview pressure is a recipe for quick hacks and hidden bugs. You'll probably spend more time fixing it than you'd ever gain.
I doubt people would wise up actually, at least if you kept it small scale. But I doubt you'd get anything of value out of it either.
Reply
Reply
It is a fast way for me to see one's coding style, it is a game (so it should be fun even to test while writing it), and they KNOW there is no trick here.
One guy (I hired) wrote a 3D pong, it kicked butt.
One guy made it 100% faithful to the original (which I liked).
Some don't "get it", they can't make it work with multiple keys pressed at the same time, etc.
Reply
Leave a comment