PHPBenelux Conference 2016
29 - 30 Jan 2016 at Ter Elst

Great job at presenting an overview of security layers, and explicitly pointing out that secure PHP code is only a tiny part of a stack that could be (in)secure as a whole.

I had some difficulty following the presentation because of 1) unreadability of slides and 2) the way you used slides.

As for point 1: the quality of the beamer and the size of the screen didn't really help. But slides with graphs would have been hard to read and interpret anyway.
Point 2: this is very personal. If i see a slide with large amounts of text, I start reading and focus on the slide, instead of the story. There were many slides that exactly showed what you told. I prefer slides that support your story (eg. what you say), instead of the other way around.

I was a little late(like 5mins, sorry for that), so didn't catch the kick-off, but could catch up easily.

The tutorial was build up perfectly, Michael thought allowed mistakes and supplied a way to get back on track again.
The way the tutorial was you could expand your ansible knowledge bit by bit, which made it very clear one was doing.

I think I hoped it would have gone a little deeper, but the where a lot of things I learned( the very basics of Ansible), I would recommend to rename the talk to "Vagrant with Ansible" because Vagrant isn't a big part of the talk.

Thanks Michael for sharing your knowledge, I would recommend you as a mentor for Ansible!

GrumPHP is awesome. I think you explained it clearly. For me the presentation was clear from the start since I was already very familiar with the problems Grum solves (especially git hooks stuff). I can imagine that doing the demo at the beginning would indeed be better since not everyone is familiar with git hooks.

Cal is very easy to listen to and seems to be very comfortable on stage. He's a good story teller, resulting in a good fit for the keynote slot in the schedule.

The message of the talk was that people get done more together than alone and that communities are therefore the most important facilitator of growth and innovation. The talk was a bit too lengthy for me (for this message alone), so that makes 4 out of 5 stars.

Great tutorial! Despite the fact that i knew most of the topics discussed, it was still a very good way to get a clear view on what to watch out for!

Everybody was very nice and helpful. No queue, despite the sold out venue! :)

Nice sit-down talk, very informative. I picked a few things from it which I already try to improve in our SCRUM team ("I don't care which meetings you had"-thing).
The animated gif was fun, for 5 secs ;-)

I enjoyed the talk, because I like the topic and I like the passionate way you addressed it. Quite nice to be reminded of how useful value objects can be!

I have a suggestion regarding the structure of your talk:

The solutions part of your talk contained three elements: separation of concerns, method extraction and value objects. These are not all of the same order. Separation of concerns is a general principle whereas method extraction and the use of value objects are more concrete solutions for specific problems that can exist in code and can be part of technical debt.

I would advise to choose a more coherent set of pillars for the talk. Either go for a more philosophical talk (talk about separation of concerns, modular vs connected architecture, trusting on framework vs pure OOP etc. etc.) or go for a more concrete talk (talk about three useful refactoring strategies for tackling technical debt).

In any case, I think some more code examples and actual usecases could save you a lot of explaining.

Final point of feedback, I think you can spend less time introducing and explaining the problem and get to the heroes of your talk sooner.

Hat tip to the organisation. Everything here was just so well executed.

With the knowledge of the workshop i took friday this talk made everything even clearer.