My basic filter question was always this: in any language you know, write a function that reverses a string. No tricks, no gotchas. Any reasonable solution will be discussed briefly and then we'll move on to discuss other things.
But a shocking fraction of people -- even ones with CS degrees from fancy schools -- would spend 30 minutes stuck trying to write that function.
That's what I think of when I hear "can't code their way out of a wet paper bag".
In the early days of computing IBM hired candidates with the right aptitude but zero programming skills and then trained them. It Worked out fine.
In the year 2014 there's no excuse for having "zero programming skills" if you're looking for a job programming computers. We all have computers, it's not like you can't practice on your own time before expecting someone to pay you for it.
And we do have existence proofs that businesses can succeed by hiring candidates with the right aptitude but no programming skills and then training them. For example see IBM a few decades ago or Zoho today. If you don't want to do that then you have no right to complain about the market supply of skilled developers.
I'm not arguing that there are no people trying to get developer jobs who have no business doing it, or that it's always inappropriate to ask algorithms or data structures questions. I'm arguing that there is an overemphasis on trivialities, minutiae, and irrelevant details.