If you are looking to learn more about the Symfony PHP framework, you can gain confidence watching a real pro slug through a few projects and pick up a lot of great, helpful tips along the way while chuckling at the real English he pervasively sprinkles with entertaining British anecdotes and self-outrage. Chris, you’re really hard on yourself, and you are by no means a NOOB! 🙂
I finally made it over the Symfony hump and must admit that I wish I learned a PHP framework much sooner. If you’re on the fence, learn one, trust me, it will be well worth your time. If you’re stubbornly refusing to look into a PHP framework, the era of “cowboy coding” is over, you will be irrelevant in about 3 years unless you adapt. Perhaps you should consider learning COBOL and specialize in migrating their COBOL code to web-based and bring them into 2003. At least they’ll be in the same millennium!
Why use a PHP framework?
You will find when you delve deeper into these frameworks that they save you a lot of time so the quality of your code and what it can do is better thought out, structured, ready for re-use, and the results will be exponentially better. Learning a PHP framework is an investment to better collaborative development environments and smoother sailing for any company who depends on a website.
Future proof your web assets
Another big reason to consider moving your web department to a framework is future compatibility. As your company grows its web assets, you may expand and find yourself in need of another web developer. The younger developers may only understand and be effective through a framework. Sure, the more experienced who don’t use frameworks may argue that they have written a few pseudo PHP frameworks in the past, but those libraries and tools they made were custom built. Without standardization and a common experience and understanding, unlike many developers share with the real frameworks like Symfony, Zend, CakePHP, Laravel, CodeIgnitor, or Yii to name a few, your company will not gain the benefits these PHP frameworks inherently provide. It’s compounding returns and with the exception of Zend, moving to a PHP framework will cost you only in time, but the trade off for the future will put you in a much stronger position with much stabler websites and code that will be written that will not only last longer, but be much more useful and effective to your company. That means more profits with compounding returns and less waste, a pretty good combination, don’t you think?