Dutch PHP Conference 2017
29 Jun - 1 Jul 2017 at RAI Amsterdam

Good talk, well delivered. I think we take a lot of the dependencies we use for granted, and getting some large scale screwups from other languages should make people rethink their strategy.

I do agree with some of the other comments in that I expected a little more "help" when it comes to actual problems that can occur (like solving version dependency mismatches or the ability to use your own fork while you're waiting for a package maintainer to merge your PR). Still a very recommended talk.

I finally got to see a talk by Christopher after having followed some of his work through blogposts and twitter. Not disappointed!
Like the blogposts, the level was just right, and the slides very clear (I'd give an additional thumbs-up for the cool live-coding inside the slides if I could!). Totally made we want to check out AMPHP.
I usually look for a point of improvement as feedback, but that would be nit-picking at this point. Well done.

Interesting, content-wise, and a somewhat novel way / reason to use ELK. As others have pointed out, preparing a talk like this a bit more might keep the tempo up.

I found the topic absolutely keynote-worthy, and the content was good enough. Empathy as a skill is so undervalued it deserves attention. From employers, but also developers themselves.

Some talks/speakers can do extremely well without slides, but I felt in this case that the combination was not hitting the mark. Putting a bit more energy into the delivery, or have bit of visual excitement would have done a lot to get me more inspired.

Great talk! Hilarious, deep, technical (it's usually so hard to combine those!) and of course.. magical. The fact that the slides were made last-minute kind of showed showed, but that's literally the only thing I'd change about this otherwise brilliant talk.

I do think this talk was brilliant: it definitely stood out compared to most of the other talks I attended. Plus I think it has a lot of potential to become even better. No need for showing code in my opinion: the concepts themselves are important enough and there were enough real-live illustrations to back them up.

Maybe some examples of how things went wrong and how they were fixed on real-life software solutions would be nice as well. E.g. how a bank or hospital got hacked, how that compares to a nuclear reactor meltdown, and how they fixed it, etc. But again: no need for code IMO.

Great job, especially considering it was your first talk and time was limited. Good delivery and all demonstrations worked very well. You should consider speaking more often!

Very clear and easy to listen (considering the subject), great job!

Good talk about why you should use several security layers but I was missing some code examples or schematics how to use that knowledge in your applications.

Nice introduction to the ELK stacker and how you solved your problem! The live demo gave you some issues in the beginning but was really adding a lot of value to the talk.
My advice for a future talk is to be more prepared, especially if you give a live demo. You can perfectly save the configuration of the graphs somewhere so the audience doesn't have to wait that long.