ZendCon 2010
1 - 4 Nov 2010 at Santa Clara Convention Center

This would have been better served as a tutorial, but it was good nonetheless.

Informative.

Nothing I didn't already know, but still a great talk. Stefan is definitely one of the most entertaining, understandable, and engaging speakers I've seen.

good share of experience

good to have the state of Zend to tell where things are going

Good talk (for what Matthew could vocalize) that, especially when code samples were shown, solidified that dedication to best-practices & clean-up the 2.0 release is striving for.

It would've been great, to encourage improved participation from the community (especially for BugHunt Days), to have a slide or two actually showing the "patch contributor workflow". Overheard developers having to "wait for alpha" before forking & contributing, which I'm sure wasn't the intended message. Of course, this can be remedied with a twitter post, but like most sessions, it's great to have a clear "now, help us by doing this, this and this" for developers to leave with.

Even as a user of Capistrano & PHPUnderControl, this was a fantastic talk. I wholeheartedly agree with many of the tools Michelangelo recommended, and for the same reasons (Phing, CodeSniffer, etc.)

Great off-slide discussion about using PHAR files in deployment, simplifying the build process, updating versions, etc.

Also, slides were actually very good, especially the "demo" slides that had video. Great timing and execution of slides.

Pretty good coverage of Memcached (which isn't overly complex from a user's perspective, which is great).

An interesting tidbit was how splitting up long-vs-short-lived cached content on different servers (for optimized deletions). Tips like this were few, but handy.

I cannot emphasize how technical this talk was. Fascinating from a CompSci Major's perspective how performance improvements were had even as PHP grew in complexity.

It would've been nice to have a "take-away" as a developer, such as simple ways to help the PHP interpreter better handle their code, whether it be highlighting particularly expensive techniques/functions/patterns, or recommending small changes to branching conventions. Perhaps that doesn't even apply, but it's always great for every talk to impact/improve development in some form or fashion.

Pretty basic talk with the golden nugget of "having an empty Bootstrap.php".

Many devs have similar projects with similar boiler-plate code/resources/plugins that have turned into copy/paste jobs. Showing how to make these more extensible and more like library components would definitely emphasize the "Reusable" portion of the talk.