I decided to keep a blog of my experience on the way to becoming a professional podcaster and screencaster. So you can call this Podcasting 101. Like anything in life, you have to start somewhere. So why not right at the beginning?
Over the weekend, I was fortunate enough to be at this year’s PHP UK Conference, in London. One of the highlights for me, as a Zend Framework developer and evangelist, was Gary Hockin’s talk on maximising Zend Framework 2 performance.
Whether you’re new to Zend Framework 2, or an old hand (can someone really say they’re an old hand after such a short period of time?) the talk covered a range of tools, tips, and techniques for increasing application performance.
After much, much, work, Master Zend Framework is live and it’s better in every way than the original.
Want to learn how to have initialized objects with minimal code and nearly no hands-on configuration in Zend Framework 2? Come learn about setter injection.
Here’s 3 simple ideas for improving Zend Framework 2 application performance without learning more code. Think Database
Do you need to use different elements of a Zend Form, in multiple locations? Are you keen to reuse the same form class and avoid code duplication but don’t know how? Come learn about validation groups.
Are PHP’s magic methods worth using? When you use them, can you truly write testable code? Let’s explore one side of the argument today.
Are TableGateways too hard to implement in Zend Framework 2? Too hard to justify the effort? That’s what I was asked recently. So I’ve written this post to show why they’re not, and how they bring great flexibility, when implemented correctly.
Recently I got to thinking about this question.
I wrote recently, that after my most recent experience on Windows, specifically Windows 7.