Lone Star PHP 2016
7 - 9 Apr 2016 at Addison Conference Center

Great talk on common pitfalls of software estimation and how to avoid them.

All the things we know, but refuse to admit. Thanks for putting the thoughts in a form that we can get our heads wrapped around, and hopefully, better express to our clients.

Excellent overview of the history of HTTP and all the new bells and whistles of HTTP 2. Good pacing, though having time for Q&A would have been more ideal. Definitely appreciated the advice on things we can do with HTTP 2 right now. Illustrations of what using preloading looks like and debugging HTTP 2 requests were great.

This was a really well presented talk. You could tell Ben was very well prepared and knew the information he was presenting. Presentation style was good with good pace - not too fast, not too slow. Great job!

Ran a fair bit under time; practice giving the talk to an empty room and time yourself. Speak more slowly and loudly. Try to look more at the audience rather than back at the slides. It may help to include assumptions at the start of the talk, e.g. familiarity with MVC, as I suspect some attendees may feel a bit lost otherwise. Define terminology as you go (e.g. not everyone may be familiar with Composer, Docker, JWT, etc). Overall, the content was good, it just needs to be fleshed out a bit.

Very interesting talk and well polished talk! While I do contract work myself, and this talk won't really cause me to change how I work, listening to this talk was both fun and informative.

great to know this history of how we got here, would love to see more examples in PHP/preloading

Thanks for a great presentation. Ouch! Uncomfortably challenging on some points. Will definitely be making changes - for the better! - in my bidding and customer management processes.

Really great talk! Loved the slide format.

Went in depth on the proper methodology to unit testing and how to change your coding to thinking about the behavior and function of the code before writing any code. Had us pair up and work thru this process of writing the tests to break the code before fixing the issue. This cause short iterations of writing tests, coding and refactoring. It really makes you think about how the code it going to function long before any major problems occur.