Programmer's conundrums

In article <20060404025850.GD20027 at alpha.rcac.purdue.edu>, Patrick Finnegan <pat at computer-refuge.org> writes: I do troubleshooting all the time -- its called debugging software. Show me some code, some behavior and a debugger and I can trouble shoot problems all day long (and fix them too, smarty pants! :). Brain teasers don't show you my troubleshooting or debugging skills. They show you my brain teaser skills. Like I said, I'm great at debugging, sucky at brain teasers. I still don't see the proven value of brain teasers. What I see is people saying they think they're useful for inferring <insert human property here> in an applicant. That's a far cry from the cold hard logic of mathematics to prove to me that this isn't a fad. I also notice that lots of people refer to using these with special qualifiers as you did. That's not been my experience. Its pretty clear that they dug these brain teasers out of a book somewhere. -- "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: <http://www.xmission.com/~legalize/book/> Pilgrimage: Utah's annual demoparty <http://pilgrimage.scene.org>