php[tek] 2015
18 - 22 May 2015 at Sheraton Gateway Suites O’Hare

Good intro to the subject. Might want to prepare more "additional resources" for people looking for more

A lot of great materials provided and also useful pointers in building app with API. It opened my mind on how to use different APIs to accomplish my project. However, demonstration on writing code on each API seems to be a bit too tedious after first few APIs? If this one is a training, why not asking attendees to try to complete some codes. It would be more interesting and more interactive experience.

While we saw a lot of code, we didn't see the actual application or working. I think that paring each block of code with a quick demo would have made the talk a bit more interesting.

Thank you very much for your feedbacks! They're really appreciated. I've shared the url with all sample codes I've presented in my slidedecks. You will find the classes, the unit tests files and a short README file for each component to explain how the code works. I also highly recommend you to look at the unit tests suites files to have a better understanding of how the different patterns works. Feel free to ask if you have any questions. I also hope I will be able to translate the book when it will be ready in french :)

Good presentation. Thanks for your time.

I thought the most helpful part was going through real world code and critiquing the design choices. It might have been even better if you devoted more time to this and showed more specifically how you would refactor. You could even frame the whole talk about that, showing the value of the various concepts you are teaching without first naming and defining them. Justify the changes; show their merits; and then explain how it is a named pattern and provide its details.

You didn't really sell interfaces much. Sure, you can implement multiple interfaces as opposed to inheriting from just one parent class, but given that you have to write the implementation code in each child class (which is mitigated with Traits), what is the advantage of defining the interfaces? The trait advantage was made clear-- to reduce code duplication. But you didn't explain (to my understanding) the benefits to bothering with the interfaces.

You ended abruptly, without demonstrating and walking through the code which ties together all of the new concepts with your original "dog with wheels" conundrum.

Great to have more tools available for testing.

Exciting to have such a huge speed improvement on an already fast language.

Thanks for this! It was extremely useful to see how to take OOP a bit further within PHP

Might be my own newb issues with OOP, but it would have been nice explaining some of the jargon a bit more or explaining some of the questions from the audience. Also slowing down the code examples a bit more would be nice.

Really appreciated this talk.