I don't think we should treat this as a discussion of good coders and bad coders. "I wouldn't hire someone who ____" is a hiring filter. And ANY worthwhile h

I don't think we should treat this as a discussion of good coders and bad coders. "I wouldn't hire someone who ____" is a hiring filter. And ANY worthwhile hiring filter will be over-aggressive. So it's more a distinction between groups that contain close to 100% good coders vs groups that contain a much lower percentage. The point of a hiring filter is to weed out bad coders, and hirers should realize that any filter you set that will weed out most/all bad coders will also weed out a LOT of good ones. So if someone says, "I wouldn't hire someone who ______", they're NOT necessarily saying, "All people who _____ are bad programmers". Instead, the smart hirer is actually saying, "People who _____ are Group A and everyone else is Group B. Group B contains many great hires, but it's really difficult to distinguish good hires from bad ones, and Group A has almost no bad hires. Therefore I'm only hiring from Group A."