Lone Star PHP 2014
25 - 26 Apr 2014 at Addison Conference and Theatre Centre

Definitely thought I would know all the things, but, I learned a couple of principles. JavaScript content was a bonus!

Just need to work on timing a bit.

I really liked this topic, I'd not seen a talk on this topic and it's obviously something that everyone deals with at some point in their careers. It' a pretty extensive topic and I think you covered the preparation well, the example questions were really helpful. I would have liked to have seen a little bit more content about some preparation concerns that weren't tech question related, however I found this talk extremely valuable and it's a must see!

Really enjoyed listening to this talk, a really thorough explanation of HTTP. I like listening to you talk, always learn a lot and you are very listen to. Thanks for the talk!

Extremely valuable experience! Couldn't recomend this more.

DragonBe delivers once again. I would've liked to see this as the closing keynote*, because it speaks to one of the most important factors in the maintenance and growth of the PHP community.

* Larry Garfield's keynote was great nonetheless.

Thorough presentation from one of the more knowledgeable folks out there. Only minor note is to enunciate a bit better or perhaps bring the mic closer.

Great talk! Enjoyed learning about the different caches. Also, Bob is funny.

Very informative talk. A few of his best practices run contrary to a few practices I picked up years ago. Now, I need to revisit those and determine if I want to change. I did like how he explained WHY he thought they were good practices.

I was intrigued with the idea of writing tests for unfamiliar code. He showed that writing tests should not be feared as much as it is. I agree with the other comments on having more examples.

Hey anonymous! As I mentioned in the talk: your infrastructure and your stakeholders are going to be a big part of how you decide which branching strategy and/or permission strategy to use. We use a scheduled release because we don't have test coverage (and the necessary infrastructure) to use continuous deployment/continuous integration. If you've got more questions about "why" please do drop me a line, I'm happy to talk your ear off about it!