Over a million developers have joined DZone.

What PHP Framework Should I Learn?

· Web Dev Zone

Start coding today to experience the powerful engine that drives data application’s development, brought to you in partnership with Qlik.

Dear Reader,

I get asked this question every now and then. It recently came up on twitter. To me, this is like a carpenter being asked “Which hammer should I use to build a house?”.

Each of the modern PHP frameworks have their strengths and weaknesses. If you are a professional programmer, you need to be aware of the top frameworks. (No, I won’t define them here, you figure out which ones are important to your particular career) You also need to be able to work in a couple of them. “Knowing of” and “Knowing how to use” are two totally different things.

There is no “right” framework, there is the right one for the job at hand. If you only know how to work with one of them, well, then you can build your house with that particular hammer.

Professional programmers should have a variety of tools in their tool belt. No, you don’t need to know how to work in all the PHP frameworks, but you will need to know 2 or 3 of them. Invest some time in yourself and your skills. Take one weekend a month and build a small project in a framework you know OF but don’t know how to use. See if it is a better tool than the one you are currently using. The worst thing that can happen is that you learn something new.

Until next time,
I <3 |<

Create data driven applications in Qlik’s free and easy to use coding environment, brought to you in partnership with Qlik.


Published at DZone with permission of Cal Evans, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}