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

Great talk! Even though I was relatively familiar with the topic, I was both entertained and educated.

I was freelance from home for quite some time. Then I got my first corporate job in an office. A lot of your talking points shined a light on thoughts and feelings I've had that I couldn't quite put my finger on!

I absolutely love your confidence in your code when shipping it out. All because of your planning process before you even write a line of code. Brilliant.

Great advice on profiling, mainly using XHProf. As someone who has used this tool, I enjoyed the examples and the learned about some features of which I was not previously aware. Michael also referenced some additional tools that I'm looking forward to trying out.

Excellent talk. Examples were very well done and easy to follow. Did a great job of covering a lot of information and answering questions.

I've always been curious as to how to determine what was taking so long, and where that was. I really appreciate that you took the time to explain the options I have and what they look like.

Outstanding trip down memory lane. I did a lot of the BBS and early web stuff Samantha talked about and I'm a bit of a computing history junky. This was a great look at where we've come from and where we're heading. Very engaging and a lot of fun. Extremely well done.

This was a really cool talk. The presentation slides, and demo were flawlessly integrated into a working Minecraft game. Quite impressed with all the things that are even possible. Really well done.

I knew nothing about machine learning or neural networks before this talk and now I know enough to get started. I still don't quite understand how the input and output files work and would have liked a little more detail on how those are formatted and utilized.

While the content itself was spot-on, I'm always a bit frustrated when talks focused on legality and compliance hedge too much with "I am not a lawyer" disclaimers. The presenter both started with such a disclaimer _and_ hedged much of the Q&A with the same.