Good talk! Dieter was presenting the topic in a very relaxed manner. And every time he brought my mind to form a question, he had the answer in the next topic. Job well done!
Subject I was very interested in, however Dieter sometimes seemed to be a bit out of his comfort zone (insisted on doing his talk in English while he could've done it in Dutch). Dieter could've spoken a bit louder as it was sometimes hard to understand him from the back row.
He clearly knew the subject and had answers for every question.
As a (new) Symfony dev, I would have loved to hear more about possible problems they encountered, how they fixed or approached certain things (bundles, keeping controllers clean, services...).
I'm with Bram on this one. The talk was ok, but I would also have liked to hear more on some of the issues you encountered, and how you solved them (or maybe focus on one issue in-depth, because of the time constraints).
I think in general it was a good idea to keep your talk in English if you practiced that way.
The biggest problem was your volume, once you were not directly facing the people you needed very good hearing to get everything you were saying.
The talk was far from as technical as i expected, but if you are talking about over a year of development and research of things you cant get all the details in 50 minutes :)
Comments
Comments are closed.
Good talk! Dieter was presenting the topic in a very relaxed manner. And every time he brought my mind to form a question, he had the answer in the next topic. Job well done!
Good talk. I may be a bit biased about the topic, but Dieter explained all the stuff we encountered in a clearly manner.
Subject I was very interested in, however Dieter sometimes seemed to be a bit out of his comfort zone (insisted on doing his talk in English while he could've done it in Dutch). Dieter could've spoken a bit louder as it was sometimes hard to understand him from the back row.
He clearly knew the subject and had answers for every question.
As a (new) Symfony dev, I would have loved to hear more about possible problems they encountered, how they fixed or approached certain things (bundles, keeping controllers clean, services...).
I'm with Bram on this one. The talk was ok, but I would also have liked to hear more on some of the issues you encountered, and how you solved them (or maybe focus on one issue in-depth, because of the time constraints).
I had high expectations about this talk, unfortunalty it did not go in-dept to show us some practical problems that the team faced.
There are already some good points made above.
I think in general it was a good idea to keep your talk in English if you practiced that way.
The biggest problem was your volume, once you were not directly facing the people you needed very good hearing to get everything you were saying.
The talk was far from as technical as i expected, but if you are talking about over a year of development and research of things you cant get all the details in 50 minutes :)