php[world] 2017
13 - 16 Nov 2017 at Sheraton Tyson's Premiere

As someone who's spent time digging through confusing Jenkins tutorials, Margaret's "here's what you need to do, the items you'll need to enable, and the stuff you can safely ignore" approach was wonderful. I would have hoped for a little more "now that we have it set up, here's all the extra stuff we can do", but this was a fantastic "getting up and running with Jenkins"-type talk.

Really great talk -- not at all what I'd expected from the title, but it was entertaining, witty and insightful.

I thought Michelangelo's workshop was great with a lot of good code examples. I'm excited to start doing TDD and was especially excited about the "--testdox" argument and the HTML output. It's really nice to be able to see exactly what your tests are covering!

Tim's talk really shed light on the benefits of providing a standard API design that clients can leverage for resource discovery, as well as clearly defining what a resource is. I thought the slides were really well put together and well designed. The workshop itself might have benefited from a little more direction in the way of implementation details, but I understand not wanting to enforce a specific paradigm on people.

The walk-through helped. I think it could be improved by maybe setting people up with a basic Slim framework and then building up examples with the attendees. Not having worked with creating APIs from scratch before, it might be interesting to work through building out a basic API together.

I really enjoyed this workshop. I learned a lot of great lessons in defining clear boundaries and creating context-driven terminology for both code and stakeholders. It was also great to see a real world example of how DDD lets you maintain readability and functionality across your entire code base by bounding context into smaller sets.

Less about the mechanics of machine learning than using available tools, but still very interesting to see it all put together.

Good talk. Would be great to hear one aimed at people who would try to prevent social engineering company-wide.

I really enjoyed this talk-- it was good to see how to tackle a problem first by defining the surrounding behavior and it gives you safety before you start refactoring. It was also nice to see how to use these tests as a temporary measure that doesn't need to live forever, only until you can get from point A to B.

Awesome talk. Shows that you don't need to include an entire framework to start leveraging their code. Going to try to integrate lessons learned into my legacy apps!

Learned a lot of great new tips and tricks! The productivity guide was incredible! I'll be using this thing every day!