Don't make them compete, make them work together!

Most people know me for my strong tie with the symfony project. Granted, when I was first looking into frameworks, symfony was by far the best and most mature PHP5 MVC framework out there. And at this point in time, I still think symfony is the best solution for the types of websites and web applications I usually create. However, that does not mean that I limit myself to writing everything with symfony.

Looking for functionality
When I want to implement a certain functionality, my first stop is usually symfony itself. If symfony does not support it, I go to the symfony plugins repository. If even that does not have it, then I look around at other frameworks. Zend Framework is a first stop usually, but also ezComponents and Solar are good places to start looking, is my experience. After Googling for individual libraries, my last option is to write something myself.

The lazy developer

A good developer is a lazy developer. If someone else has already built a specific functionality, why the hell would you start from scratch? If something has been well-programmed, it will be easy to extend and overload specific features that you'll want to use in a slightly different way. And this is exactly the reason why one should not just focus on a single framework. Of course you can always add new stuff yourself, but if there is already a good library out there that does it, why not use that instead. If you look at the current popular PHP5 frameworks (Zend Framework, symfony, Solar, ezComponents just to name a few) then you seriously cover most probably 99% of all common use cases for web applications.

Focus on the important

Instead of writing a new custom library for your project, you should be lazy and use an already existing component, even if it's of a framework you're not using yet in your current project. That will allow you to focus on those parts of the project that can not exist in already written components: Custom business logic, your project's database schema and its related functionality, the views and templates of your project, the usability and accessibility of your application. These are the things that are really important for your project at any time. Re-using existing code will allow you to make deadlines more easy.

Now, I am not saying that specializing is a bad thing. Especially for small development shops and for supportive departments of companies whose core business is not web development, it is probably best to specialize in a single framework. As you've done your research, you've probably found a framework that covers a huge part of your use cases and your developers will pick up easily and deploy quickly. Specialization is good in those situations, but don't stick inside that box. Even though you focus on this one framework, be aware of what is out there. Every time you're thinking "that sounds like something for which a library already exists", make a round through at least the most common frameworks and google. See if there's something usable out there already.

Use the right tool...
Too often have I seen companies focussing on a single tool just because "it's the standard for our company". You should have a wider look. You should use the right tool for the job. Everybody knows (well, should know!) this by now. It should be your mantra. So that also means that you may need to think out of the box and use a tool that is not your standard tool for specific stuff. And with that, I'll leave you to look not just at your own favorite library but at other tools as well.