PHPBenelux Conference 2018
26 - 27 Jan 2018 at Ter Elst

Interesting topic but try to "see" and talk to your audience. I found it hard to follow considering the fact you talked very quite and a lot of the time to yourself during the workshop (actual coding).

Talk highlight problems related with poor naming of variables, methods, classes etc. Content of presentation were very good, Pawel speak in quite monotonous way so public speaking part for sure can be improved , but I would really recommend to see that presentation to each php developer.

Awesome very needed talk, we need more talks like this one. I am working with legacy applications and use simillar techniques in daily work, but I needed to found out and learn such aproaches myself - such talk would help me a lot a few years ago.

And i catched elephpant at the end so... the best talk of the conference for me ;)

Interesting talk with a speaker that's nice to listen to and has a good interaction with the audience. However, it was a bit short. I understood he dropped one of the subjects, because of time-issues. 5 stars if the talk would have been longer.

Great talk, nice topic and a good speaker.

Advanced talk about what happens behind the curtains. It was really interesting to have a look at this, although I got lost somewhere near the end. But it was really nice to listened to a speaker who has such a deep knowledge of php and its internals.

Great talk. One of the gems of this year's conference. It reaffirmed that we're using good practices already (yay for the Symfony security check in CI :-) ) and provided some good pointers on where to improve.

I think this talk was aimed at the wrong audience. The speaker showed beginners-mistakes examples, and I think most attendees were professionals who're already passed these mistakes. There were some good questions from the audience afterwards (like "what if the domain has a non-English vocabulary?"). So if you'd do this talk again, I would make it more advanced with more real life examples.

Oh, and cats. It really needs cats.

Prior to the talk I couldn't come up with why anonymous classes add anything useful, I was surprised to stand corrected! Although I wouldn't agree on all usecases (I felt that the use case for the first example, with the locations, could be solved much simpler, and I think that private methods shouldn't be tested just because you can now) there's still plenty of situations where anonymous classes are a valid addition to the toolkit. Thanks for the insights!