[lloydgrossman]

> So you'll end up with team players but with nobody who will actually get the job done.

There are plenty of developers that are capable of writing code and explaining how and why they've done it. Your difficulty communicating ideas doesn't directly translate to being a better developer.

>The better way is as the interviewer to do your homework and to engage on the level of the interviewee

I'm not sure you've ever reviewed resumes, but they pretty frequently absolutely suck, targeted or not targeted, or otherwise not accurately representing skills. It can go from completely clueless "buzzword bingo" to "obviously I'm skilled enough to not need to mention the silly stuff like TCP"

>Realize that your company is as much in the hot-seat as the candidate is.

...and for those companies that do understand that?

Where is the substance to this comment? What stance are you taking or solutions you proposing?