I'm responding to a comment that my time blocks of PHP experience are not long enough for a given job. I address this in several parts:
For the rest, see elaboration below this list:
It runs on my web site. It's meant for anyone to create a user and experiment. I also encourage you to talk to the real estate broker who commissioned the work, Craig Hatcher of Georgia Residential Realty.
It only recently occurred to me that perhaps not every highly paid developer can complete medium-complex applications such as this from scratch.
I haven't released the source code for reasons I discussed at some length with the interviewer. In brief, the goal was to have a running example, but I didn't want to spend enough time on the code to get it to opus magnum status--clear enough code that the documentation would write itself. With that said, I'll release parts of the code that I'm proudest of upon request, or perhaps all of it.
The original version isn't online but had some cool features. The person who commissioned this will endorse it. She can be produced upon request.
What remains is JS and not PHP, but JS is relevant to the job, per the interview.
In addition to the above and what is on my resume as bullet points, see some PHP source code and articles below, some of which may not have been on the version of my resume in question:
In addition to commissioning the real estate application, Craig Hatcher is the one whom I stepped through a WAP--Windows, Apache, PHP--installation while I was on top of a mountain. My interviewer remembered seeing that story on my resume months ago, at his previous job. Craig is disappointed that he hasn't told you that story.
If it needs emphasis, this episode means I not only know enough to install WAP but enough to communicate it to someone less technical, from a mountain with no (usable) internet phone or even anything to write with. Listing my technical communication credentials would be another document.
I've been freelancing as a way to avoid working 9am - 5pm; we discussed this during the interview. Given that I usually avoid expensive-to-you recruiters because they usually can't solve the 9 - 5 problem, I wind up with 1 - 2 employee companies. Given this, most projects petered out for one of two reasons:
I'll be happy to discuss in detail what happened to each project, and you can verify it with the client.
In a number of cases, the code conflict between my up-to-date development server and the outdated production server cost time-money we didn't have. I could try to describe the client's reasoning for keeping their servers, but I'll admit that this was likely an inter-personal failure on my part: I should have built an overwhelming argument for moving servers.
In one case, I was asked to use a version of Fedora Core Linux that was 5 years old and pre-dated "yum." This was absurd and led to great technical grief and waste of time-money.
I want to point out that I want "complex" virtual servers with root access. That's what I'm confortable with. I love Amazon Web Services EC2 despite its being "complicated." I generally can't tolerate shared hosting--servers for dummies.
I hope I made it clear during the interview that I am looking for stability. I don't want short blocks of anything anymore. This is an opportunity to gain stability and solve the 9 - 5 problem. That's all I want.
Some PHP developers with long blocks of time have analysts giving them specifications, they do the same thing for so long that they rarely encounter a new challenge, and they have people who know more to ask questions of. I haven't had any of that. I've been alone in the wilderness getting my trial by fire. I'd like to come out of both that heat and cold, but that experience has made me better than most of them.
I think I left the impression that I had never used a PHP IDE / debugger. To clarify, I admitted my foolishness of not doing it until recently. As of a couple of months ago, I started using NetBeans. I used Eclipse for Python before that.