php[world]
10 - 14 Nov 2014 at Sheraton Tyson's Corner

I'm not a WordPress developer but I learned that I could be easily enough by taking this training.

Excellent talk with a number of great points.

Why can I not give more stars. I told Eli that if he did not make this a keynote at Tek, I will not be going

I really enjoyed the talk and it was a great justification for me as I am following most of the practices outlined. I would like to see you remove the use of anonymous factories in the demo

I came away with a better understanding of the WordPress philosophy and the changes that have been made over the years. Andrew has a very engaging personality and is an enthusiastic presenter.

Saw this presentation in Gothenburg (2014-11-15) at DrupalCamp.

"Jam" is really engaging and entertaining. The topics he brings forth are important and can not be talked about too much at the moment. It was an interesting collection of arguments and examples that will be put to good use when I meet my students. :-)

Unfortunately the decision to bump the JSON REST API neutered the talk's content a bit, but Konstantin gave a great overview of what's to come with WordPress 4.1 and beyond.

The purely Q&A format can be risky (did Eli have more prompts in case nobody in the audience brought questions?), but the session went quite well. It seemed to be heavy on the WordPress/Drupal side, though Symfony and Zend had a fair amount to contribute as well.

Perhaps in the future it would be beneficial to remind people during the morning announcements, orientation emails, etc. to be formulating questions in anticipation of the panel to ensure there are enough questions without Eli having to act as moderator.

I had the pleasure of eating breakfast with @webchick just before her keynote, and she was just as relaxed and casual during lunch as she was on stage. Excellent, well-informed speaker who is clearly passionate about the Drupal community and its future.

It was also refreshing to hear a representative of that community admit that there have been some missteps in the past (particularly the "not made here" mentality) and the steps that the team is taking to not only make Drupal 8 a better product but help guarantee its future through point releases and leveraging powerful third-party libraries.