I have no "findings", no "conclusions", but I have some thoughts on my continuing goal to help bad/nominal PHP programmers become better PHP programmers.
The first question I asked is "Is there really a shortage of good PHP developers?" While I didn't get a specific answer the general jist of it is that yes, there is a problem with finding good PHP developers. Now, some of that may that the people responding ARE the above-average PHP developers and so there can often frustrations in figuring out how to work with developers who don't yet have the chops that they do.
A lot of people also didn't like my "what are 6 of the 10 PHP variable types" question. I make no apologies for it. Any developer who has spent any amount of time programming in PHP will have had exposure to them. ANY PHP developer should be able to get at least 4. If you've never realized that there's a reason to use === then, no, I wouldn't hire you. For someone who is thinking through what their code looks like I would think you could figure out at least two more. And if someone calls me on the error and gives me the correct number of variable types, then I can be reasonably certain that they know their stuff. But, like most things, it's A qualifier, not THE qualifier. If they send me a case of Chimay Bleue I might overlook it.
I also had other discussions from people who don't think that programmer's should have to have a certain level of memorization because you can always look it up. Sorry, but I have to disagree with those people. If you cannot tell me, offhand, what a callback function looks like then you probably don't have enough experience. If you can't tell me what PDO is used for then you probably don't have enough experience. For various levels of developer maturity there MUST be some things that you are required to know offhand.
One of the things I've also found a little interesting is that there is some resistence to standards. The argument goes; developers get better by different means and so having something set in stone to evaluate them is difficult, nigh impossible, to do. Perhaps, but I go back to other industries. They have been doing it for years. Yes, it WILL be imperfect. No doubt. Also, nobody will meet them perfectly. But if managers, recruiters and new programmers don't know what is required how can they ever become better other than by trial and error? The goal here is to decrease the "error". Or maybe people are just argumentative. I dunno.
That said, there were a few suggestions that were good which I will take into consideration. I have a little too much to do this short week for me to really get into it. So, this, I guess, is a blog post without a purpose.