php[world] 2017
13 - 16 Nov 2017 at Sheraton Tyson's Premiere

A firehose of information! This really needed to be a full-day workshop in order to be effective. Christian has an impressive command of the material and obviously put in lots of work to prepare the repos. I'm torn between giving a 4 or a 5 because I got lost for a little while, but that's my problem. :)

I hadn't heard of Travis or Scrutinizer before this talk. Both are incredible tools. Christian effectively demonstrated how useful the full deployment process is, even though it's a pain to set up and learn. I'll be coming back to this presentation and the associated files for a long time.

Very useful content. I really like how the speaker was upfront about why she prefers questions after the talk.

Wow you did an amazing job on your slides and all the details you put into your talk. You talked for 2 1/2 hours straight you must have been exhausted.

My only suggestion for next time is to limit the time you spend writing the code and tests during the presentation. The important parts are all the steps around the code/test themselves.

Nice example code and useful information on setting up and getting daemons running.

Good examples from your own work.

I liked the way you built up the stack of things to pay attention to.

Took his time, explained the challenges of legacy code and both the need for characterization tests and the methodology. His examples were clear and relevant without being too dumbed-down. He answered my questions afterwards.

Still a 5/5, but the acoustics in the main hall are quite bad and speakers need to adjust accordingly: slower, louder, and project! This talk should have been in a smaller room.

Thanks - very helpful talk with good examples.

Free food; what's not to like?

Pros: Michelangelo clearly knows his stuff inside and out. He projects confidence without arrogance. The talk gave me a list of tools and practices to at least research, if not actively implement. The Simian Army discussion made me think about how my organization could be more fault-tolerant.

Cons: Needed more implementation detail, perhaps in discussing *how* a multi-provider, multi-region application can be set up. He (and all speakers in the mail hall) was poorly served by the room's acoustics.