It's a really cool, useful application that helps people in the real world do really important stuff.
However -- it's not build with the latest, "coolest" technology.
I find a lot of programmers turn up their nose when asked to work on something that's not using the latest beta buzzy framework or language.
Instead, it seems like they'd rather work on the latest doomed social network craplication as long as they can program only using libraries with version numbers < 1.0.
So how do you present an opportunity working with a really cool, useful application, when it doesn't use the latest tech?
What's your Joel test score? http://www.joelonsoftware.com/articles/fog0000000043.html
It may be an indication why developers are avoiding you.
Hadn't seen the Joel Test before -- thanks for pointing it out.
1. Do you use source control? Yes (Git) 2. Can you make a build in one step? Yes (one command) 3. Do you make daily builds? Yes (continuous integration) 4. Do you have a bug database? Yes 5. Do you fix bugs before writing new code? Yes 6. Do you have an up-to-date schedule? Yes 7. Do you have a spec? Many 8. Do programmers have quiet working conditions? Yes (remote) 9. Do you use the best tools money can buy? Mid-range 10. Do you have testers? To an extent 11. Do new candidates write code during their interview? Yes 12. Do you do hallway usability testing? No
So we've got like a good 10/12 (I'm giving a half point each for 9 and 10 :)
Your problem is that PHP has probably the worst reputation of any programming language since COBOL.
(I count among them, and yes, I do remember enough to somehow get by in ISPF on IBM mainframe ;))
Also? The way you framed this question seethes with condescension. "beta buzzy framework" and "craplication" and "version numbers < 1.0" suggest a very negative attitude. Perhaps potential employees are reacting to this perceived hostility, not the lack of hip new tech. I might not mind less than bleeding edge, but I don't want to work for or with Mr Youkidsgetoffmylawn. And I AM an old fart who has been doing this for 20 years!
I have been programming for a long time now (~26 years) and I do tend to roll my eyes every time some fancy "new" language/framework/library comes out that's just a re-re-re-implementation of something 20, 30, or 40 years old.
It's simply not practical to keep rewriting large, stable applications using a completely new language and architecture for marginal benefits on an ongoing basis.
I've programmed in everything from BASIC to Pascal to C/C++ to C#, Lisp, Python, PHP, Java, Javascript, can't even rememeber what else and let's be honest -- there's no silver bullet.
They all have their strengths and weaknesses, and they all compile down to machine code.
I just have trouble understanding why people refuse to work with language or framework that's more than a year old.
That said, my own coding is currently leaning toward Node.js for server stuff. I'm using Neo4j for data and it turns problems right on their ear - for my space (not all spaces), it's a million times better than relational and a thousand times better than document databases. So I'm looking for languages/frameworks that make my particular use of Neo4j more graceful. Started with Rails, but gave it up as the ActiveRecord ORM is kind of Neo4j-hostile in practice. I expect this is true of most ORM solutions (hence the R, for "relational"), so maybe I can make it better in a lighter-weight system.
At any rate, there are no silver bullets, but plenty of wooden ones. I lump PHP in that category. If there's an existing PHP app, then by all means maintain it, but don't use it for new projects!
It's pretty simple economics. If you are using "cool" technologies, you basically get a discount on your developers because there are so many of them that want to work with the tech. The less desirable your tech stack is, the more you have to pay (in cash or benefits) to make up for it.
In fact, often the most expensive "hired guns" will perform the worth in the long term.
What I'm looking for are people who are genuinely interested in the problem space.
I don't think its popularity with beginners is what earned it a 'terrible reputation' though.
There are quite a few other good reasons to not like it.
Do you offer part time? Telecommute?
I'd jump at the chance to work with Lisp (which is far older than php) because it's a joy to work with.
I'd dearly love to work part-time so I could devote more time to writing and personal projects. And I'd love to be able to telecommute so I could do some traveling while working. And for those opportunities I'd happily work in Pascal, BASIC or even COBOL.
But I just can't bring myself to touch php again.
Also, If you haven't yet, take a look at composer and packagist. Their are several cool php libs up there.
I am also pretty interested in knowing what are you doing about this problem, because my forte is php and JS, a bit more better at at php, and i am pretty confused about which tech to make a product I have in mind in. Since its a distributed system, PHP might offer a better reach (also because of its popularity as "easy" amongst non-devs). But JS over node is a much better lang to work with, though it would hinder getting talent and traction and would require huge amount of marketing etc.
In my circles there are folks still writing and building new tools for the Commodore 64. Same old 6510/Commodore BASIC but employing new programs with new methods and some new add-on hardware.
So, as another respondent asked, are you offering them the ability enhance and update that older yet cool useful application (using the tried and true technology), or just merely maintaining it?
If you can't convince such talent that you can offer a career, then you may be screwed.
P.S. Is PHP significantly coincident with such "career" type positions, these days?
