Good to see a recap of features I'm missing out on.
I'm not really following what Symfony is doing, I just know it works for most of my purposes. That's why I attended, by hearing some pointers to features I'm unaware of I might more easily convince the business it's worth-while to upgrade instead of keep piling up deprecation notices.
The presentation was a bit rough, the slides were not really styled and could do with some colors or graphics to make the presentation more engaging.
I also had the feeling you are not a regular public speaker, but keep giving talks, you know your stuff, you just need some practice to be more relaxed in front of a crowd, I think.
About the content, there was quite a lot packed in the lists at the end of each minor release.
I think it would be better to pick out some key selling points and focus on that, the question I would like answered: "What do you think the three most interesting features would be in Symfony 3.1/2/3 for me as a developer who uses Symfony everyday on legacy projects?"
More than that certainly gives a more wholesome view on what the Symfony devs have worked on, but for me it gets a bit to chaotic. Especially when you skip through the list, it's quite difficult to read the text and follow which feature you are commenting on.
So in short, less lists (distraction by text on the beamer), more talking :)
If you reduce the number of features discussed you might, as the other comment suggests, give some examples of how it makes my life as a developer easier to use the autowiring functionality for example.
Some pointers as what you are giving up (eg. explicitness of your code) or problems you've encountered using the new features would also be very helpful.
Thanks for the talk, I also learned stuff. Keep giving the talk and improving it.
I think the PHP community really benefits from experts pointing out some key-features which make everyday development easier for the rest of us in an easily digestible way :)
As this was the first time this talk was done, it was really good.
It's kind of a talk to motivate people to apply a multi-service architecture if it suits your project.
I really appreciate some pointers as when not to use this technique. Lots of talks try to push a technology/paradigm/architecture and don't mention the projects for which you would kinda, better use another maybe more traditional approach.
Some consequences for the way multi-service projects should be developed were discussed (automating everything: testing, deploying, monitoring) and the argument is made that this will make your development process more mature and faster.
So it's nice to see the balance of investment and return, instead of focusing on just the return if you do it right.
The talk is a bit abstract as there are not many tools discussed that can make it easier to move to, or start a project with multi-service architecture in mind.
There are, however, pointers to bigger, more established ways of making up the elements needed to run a successful multi-service application (like containerization and discovering and defining bounded contexts).
So all in all, a good starter for PHP developers who would like to wrap their head around multi-service applications, but certainly not a talk packed full of tips and tricks with certain tools you can download and work with today.
Multi-service applications still seems like pioneering work in the PHP world.
Very interesting. Like I say, perhaps adding an extra slide explaining that you need to understand asyn way of working be able to move to µServices could be interesting. Like you say at the beginning, the naming should be change to something else to help people to focus on the content and not on µServices. (perhaps inter-autonomous-(multi-)services?)
Very intresting, but I was hoping to have something a bit more dynamics and with more example on what change and how it's intresting.
I learn stuff, so it was good !