Talk comments

I really appreciated hearing the front lines perspective of a mobile developer working with APIs and web apps. Good reminder for why HTTP standards, and consistent interfaces are important, even if they aren't directly impacting your own work. Loved the [Loading...] slide bits!

This talk was exactly what I needed as a Laravel 4 user that hasn't really been tracking what's new in 5. The bullet point list at the end was helpful, but a little overwhelming, particularly in contrast to the deep dives on earlier topics.

Excellent presentation. It's helpful to have someone drag my head out of the weeds to see the complete picture of what all those lines of code are about - the end user.

It was good to see this topic put out on the table for open discussion. The question format was well thought through as well. Thank you to everyone who participated. There were other topics I'd have liked to see covered, but that's just as much on me for not asking the questions. The only critique I had was that I'd theorize that the people that chose this talk were probably on the higher end of the awareness bell curve regarding this issue. I would support doing this as a keynote.

Again, thanks to everyone who made this difficult conversation possible.

Some really great points about things that we often overlook in our haste to finish and get the job done. I especially liked her recommendation not to immediately act and fix a major issue, but to make it known so that the proper actions can be executed.

Good presentation of a very complicated subject that I've only had surface level exposure to. Of I any talk I went to I probably took in the most information from this one. That said, I could have used more guidance on what were the key points and recommendations to walk away with, maybe a summary slide at the end? Props for taking the deep dive on this topic.

A great talk about why open source is important, and why it is important to give back.

Great intro to Hack, solid information, and excellent presentation. I was particularly struck by the idea that the "performance/speed" gains are best thought of as "developer performance/speed" gains. I would still like to hear more on how to get started with Hack in a large legacy codebase. Any recommended approaches for slow role? Git strategy?

While I don't use Laravel 5, it was interesting as an outsider to see some of the things that are coming about in the framework.

Only complaint was some of the red/pink text was hard to read, but that was an issue with the projector more than anything.