php[tek] 2016
23 - 27 May 2016 at Sheraton Westport Chalet

Security basics were presented very clearly. Code examples easy to follow. The "bank" example is a good one. Pretty much relevant to any human on the earth.

Highlight of the conference. Great job and great energy on stage.

A fine way to kick off the conference. I thought the section of looking at photos could've been a bit shorter, though.

Great job. Simple easy to follow code examples. Nice job connecting it back to PHP (what's different). Answered questions from audience well.

I thought this was very well done. Packed a ton of material into a short talk. Just the right amount of time spend on each item and the pacing was good.

- Didn't fully grasp all the inputs and outputs when setting up fann
- Finding commented source code was good example, but not as relevant to me. I work in ecommerce so was thinking about recommendation engine which you brought up. Wondering if you have experimented with other examples?

It's always good to hear why others are not adapting a new release. The speaker gave some clear math on why its too early to adapt. Not to mention that there isn't anything super beneficial with the new release considering the work it would take to get there.

Adam is a great speaker and did a good job presenting the topic. I'd previously heard phpdbg was just for internals development so I was curious to see how Adam would present it and he did a job convincing me it can also be useful for normal PHP app debugging.

Good overview of a few CLI frameworks/options for PHP. I enjoyed the talk and walked away with a few new tools in my belt.

This is a pretty complicated topic and Ian did a pretty good job walking through what he was doing to demonstrate improvements. I think all the setup/tear down he had to do to switch between demos distracted me a bit and I got lost a couple times. Perhaps some overall benchmark data initially would have helped me to get an overview of what we were going to see and if the roughness of the transitions can be smoothed out it would help too. Specifically maybe not having to check out different branches, rerun composer, and then launch Docker would help. If each were in their own folders with composer already run and Docker already online it would be quick to switch to another tab and show the results.