ZendCon 2016
18 - 21 Oct 2016 at Hard Rock Hotel & Casino

I think I could have easily rated this talk a 5 if I had a good depth of experience with Docker already and I was sitting in the first row, but neither of those things were the case.

The first issue is not really the speakers fault, as the talks this time around did not have the target audience skill level or prerequisites listed, so I didn't realize it would be more for intermediate-level containerizing folks.

The second issue is, but can easily be fixed I think. I have perfect eyesight and was seated around the middle of the room, and some of the content on the slides, as well as some of what is shown in the demo, was really small and difficult (sometimes impossible) to read for me. Struggling to try to see or to try to determine if what I'm NOT seeing is a big deal to be missing tends to be a distraction. However, those same slides and portions of the demo also had a lot of whitespace on them... so expand to fill! If some of the demo content can't be magnified, then perhaps either move those portions to the slide deck, or if it must be part of the demo, have some screenshots available as a bit of a "OK, I know this part is hard to read. I can't resize the real thing, but this is what it looks like *shows screenshot*."

Great talk overall, though. I'll be sure to attend it again after I've gained more experience with Docker and have the background to get more out of it.

The speaker was very knowledgeable on the subject, understandable, articulate, etc..., but I think the slide deck being as text-heavy as it is might have hurt the delivery of the talk. If I've got text in front of me, it's hard not to read it, and reading it means I'm not able to pay full attention to the speaker. The slides are excellent reference material which would serve well as post-talk notes / summary that could be shared, but I think tweaking them to be less wordy during the talk so as to not draw attention from the speaker would help a lot.

Also, this talk felt like more of a high-level look at building a highly available PHP application but didn't dig TOO deeply into any specific thing, which is not what I would have expected after reading "[...] and how to build one" in the talk abstract.

So, both the speaker and the raw content of the talk are perfectly fine, but I think tweaking the packaging, delivery, and expectation-setting via the abstract would make this a really, really excellent presentation.

Great talk that covers both some ways to just look at your code and know if it's good or not as well as tooling to expose quality metrics in a hard to game and ignore way.

Adam does a great job at providing both detailed slides without overloading you with information. Most other speakers would wind up with slides with tons of bullet points and no real detail. The mix between dense slides to then focusing on the bullet in question is well done.

Fantastic talk. This is the type of keynote I'd like to see more of at technical conferences. I've watched it before on YouTube, but getting a live refresher was great.

I think my throat would have gone dry from all the opportunities to say "I told you so!" to some former colleagues/managers this talk generated. Keeping developers happy and motivated is so, so easy and so many organizations drop the ball and fail to pick it back up before their best people leave, and their "not the best" people always stick around way too long and slow the progress of their careers.

IMO, this presentation should be required viewing for all of the "Powers That Be" at any organization, as well as for anybody who has been working at the same company longer than a handful of years "just in case".

Well done!

Major kudos on the abstract. I could have stopped reading after the first sentence and known this talk was for me because the popularity of tools that don't look as good "under the hood" as they do on the outside has always baffled me.

As for the talk itself, I don't consider myself a pure perfectionist, but I'm a lot closer to that than to a pure pragmatist, so a lot of the content gave me some more perspectives to consider that I hadn't before. I've always started building components by building out some interfaces/skeletons/etc because that's the way I've always done it and it's the way I know it's going to look... so the whole approach of coding out how the syntax for the different ways to use it would look like first, then worrying about implementation details, is something I'll definitely keep in mind to try first from time to time to see how things turn out differently.

I hope the slides will be made available for this, as I'm not the best note-taker and there are a few things I want to refer back to. :)

Great talk! As a long time Composer user, I came into this talk thinking "10 things *I* didn't know I could do with Composer? Oh really? Let's see about that!" Even though a lot of it wasn't new for me (not the speaker's fault, I've been using Composer a LONG time), but I still got A LOT of useful stuff out of this that I didn't know about before like --classmap-authoritative, conflict/replace/provides, and show/why/why-not, so I'm glad to chose to attend this talk.

If the speaker hasn't already built a talk around the "10 Things You Already Knew..." intro slide for complete beginners to Composer, he absolutely should!

The delivery was good and the historical content was interesting from an academic perspective. The future stuff would have been interesting / exciting for laypeople, but as developers, I'm sure many of us have already imagined how much more sophisticated smart devices will eventually be or have even seen it portrayed in sci-fi, so it seemed a bit speculative and didn't really seem to fit. My favorite part, actually, was the very brief GraphiQL example. I've heard GraphQL mentioned a lot in recent months and never really looked into it, but the very, very short demo was enough to get me to think "oh, cool. I'm definitely going to check this out."

It shouldn't be surprising that the most technical portion of a talk was the portion I liked best, given that this is a developer conference. I'd really love to see more of that sort of thing in keynotes!

Not much to add here. Second time seeing this; an entertaining insight into the types of people that contribute in various ways. I think the message of this talk is not "categorise" as Lee puts it, but to say "you don't have to be a rock star, you can contribute in other ways than just being a project lead" etc.

Great talk, nice and in-depth - I think maybe some info about state snapshots (as discussed in above comments) would be nice to include for next time, but otherwise nice, thanks :)