Recently I received an RFP for a CMS project. Now, my agency is pretty well versed in CMS gigs -- everything from tyrannosaurus-sized custom systems to making quick work with WordPress and a handful of plug-ins -- we've done it.
However, as with a handful of other RFP's I've had in the past, this one had a bullet point stating "Change to PHP scripting language (currently ASP)", and it got me thinking: When did we developers begin letting clients dictate what programming language to use on a project? Aren't we solution providers? Shouldn't we choose the best option for our clients? An uneducated client stating the technology to use on a project is like me telling a mechanic working on my car that he should be using Matco wrenches, not Snap-On -- a bit ridiculous, no?
Don't get it twisted, this isn't a quarrel I have due to lack of means; PHP, ASP, .NET, Python, whatever it is -- my team and I are ready, willing, and experienced. This is about purpose and principal. Never do I feel that a client should tell the expert they've hired what tools must be used to solve the problem. Not only could this hinder the project timeline, development efficiency and budget, but it also puts a level of discredit on the developer/agency in how they may effectively be able to provide their expertise to the project.
When it comes down to it, I feel PHP is no better than ASP or ASP.NET or Python or any other language, if it's not written properly. Procedural PHP is just as bad as procedural ASP, or even improperly written Django/Python or a RoR application. The server-side programming language is used [primarily] to retrieve data from a database or to promote code modularity & reuse, etc. The language used should have no bearing on visitors experience, ever. Honestly, with the many classic ASP years behind me, I'm positive I could write an ASP app that does everything a client would want and they'd never know the difference.
Now, I agree that there is good reason for a client to suggest a specific technology be used. Building a classic ASP application at this point in time isn't exactly wise; there are far better choices that ease and expedite development. Also, having an application written in RoR might not be the best choice for some clients as it may be harder to find a developer or agency who is adept enough to pick up the project later down the road. But that doesn't mean that because PHP developers are a dime a dozen [no offense, please] that technology decisions should be based upon this! Next up would be a client requesting a language because they already have an internal team familiar with maintaining said application in said language -- a very good reason, I do agree. Finally there is the infamous open source argument. Now, this honestly could turn into a whole new topic at hand when debating open source vis-à-vis proprietary languages, so lets not go that way. My thoughts are this: open source or proprietary, what matters is that you can utilize what you are using to it's fullest potential to develop the best application possible. Using PHP because a client threw it out as a buzzword isn't a good enough reason -- what if the client threw out classic ASP as the requirement, what then?
I'm not really sure how to wrap up this entry except to say this: Do what is best for everyone. I think I have a good rant, but in the end it's all about commerce. If it's an unjustified buzzword the client threw out there but you can deal with it, keep your mouth shut, do your best work, get paid and add another piece to your showcase. If it makes you feel better to try and educate the client about their decision, and you feel they will listen, by all means, go for it! On the flip side, if you don't really need the headache of the job or a client who knows best, bow out gracefully. A disaffected mood will usually radiate, and if you're not good at handling it you may ruin any relationship with the client and your quality of work will suffer -- it's not worth it.
