Dutch PHP Conference 2019
6 - 8 Jun 2019
at RAI Amsterdam
Talk comments
The idea of the talk was good, but to be honest I didn't found the presentation very good.
Some tips:
Be sure to have a relax standing. The way you used your laptop without a presenter did feel not natural. There was a lectern you could use to have your keyboard in reach. Or use a presenter to navigate to your slides.
I'm not sure if you used notes or something like that on your screen, but I got the feeling that you where got lost during the talk about what you wanted to say.
Good talk and strong presentation. I will look back to the slides multiple times for tips and reading material.
It was a very good start of the day. The talk had a funny start with where it wasn't about and a nice explanation of a good idea to improve the skills of your team.
The idea with live coding was nice, but I had the feeling it was a little bit random refactoring without a real focus or end. I feel that Pim is a good presenter but I suspect something else for this talk.
There where some nice points to thinks about, but I found it difficult to follow.
And I didn't had the feeling that the most was about a tech lead but more about a general manager.
A very informative talk
I learned a lot. Christian is very knowledgable and was able to explain both the theory and the practical implementation clearly, so the whole thing was easy to follow.
Also he seemed to have incorporated enough slack to be able to answer individual questions and problems, so it never felt rushed. That's a quality I often miss with other conference tutorials.
This was great.
Nice talk.
I don't do any wordpress stuff myself, but good to know that not everything has to be done pointy-clicky: there's a CLI solution out there.
Nice talk.
Maybe make it more explicit what problem the Liip serializer is trying to solve.
It seems to me that it generates a class on the fly (which is then probably cached or something).
This class could also have written by hand, which is a normal thing to do in software development.
Generated code has a tendency to perform badly and Liip serializer tries to avoid that problem.
Did I understand that correctly?
I found it a nice introduction to Rector, it was surprising that it was mostly about that tool. I missed some more examples about creating own rules.