Ski PHP Conference 2014
17 - 18 Jan 2014 at Salt Lake Community College

A nice overview of the different techniques that separate "feel-good" security from real security. I would have liked to see the rest of the presentation that got cut out due to time constraints.

It was interesting to hear that Chris is retiring this talk soon, since people like him have helped make the information widespread enough to be common knowledge. A great explanation of exactly why you should be testing, how to get started, and techniques to apply, and pitfalls to avoid to keep your code testable.

Good examples of how to use several common Bootstrap components, and a good look at using the grid system for responsive design. Would have liked to see more about getting started, rather then diving straight into an existing Bootstrap project. Since the talk came up very short, it could probably be padded out more with a getting started section, and some exploration of the Javascript widgets that Bootstrap provides.

I can't imagine the amount of courage it takes to talk about something so intensely personal in front of a room full of strangers. I was honestly having a hard time holding myself together while listening. I have no doubt you've helped a number of people by being so open about this difficult topic. Amazing job.

I thought using WebSockets to control the presentation on the attendees' laptops was a really impressive way to show the power of the technology. It was also good to see the tie-in back to the React presentation, showing how they work together. I also appreciated hearing about the graceful fallback when WebSockets aren't available, and the pros/cons of those fallbacks.

I think this was a great introduction to a framework that will only get better with time. There were a few slides which had the "wall-of-code" overwhelming feel to them, but overall, the examples did a good job showing what React is capable of. Maybe consider adding some examples of projects using React in production, and explaining what their use cases are that led them to choose it over a more traditional framework.

We've been using puppet to handle our AWS provisioning, but we haven't made the leap to using it for individual developer environments. I had looked at Vagrant before but it always seemed a bit intimidating. I came away with some great ideas to try out, and the examples really helped clarify.

A great into to what looks like an interesting framework. I'll be putting it on my list of things to putter with. I feel like I've seen the automatic response formatting (string->html, array->json, integer->error code) before in another micro-framework, but I can't recall which one. The nested routing stuff is pretty sweet. Great job all around.

I like the idea that you are responsible for all the code you push out to your users, even the stuff you didn't write. In practice, it might be a bit difficult to maintain a purist approach to this without devolving into NIH syndrome. On the whole, it was good to hear an advocate for smaller composable components over large monolithic frameworks.