Good informative talk, although the presentation bit might be worked on a bit. Doing it more often will probably help. Putting a bit less on a slide and showing more slides might also help making the talk a bit more dynamic and feel more "alive".
Also try to include things you reference to on your slides, even if only as a small note on the bottom.
I already used the suggestion "don't make it a nano-service" the monday after the conference.
Good informative talk, excellent explanation of some essentials that many people get wrong.
Was hoping for a bit more on how to setup, but that is hard to do in such a short period.
Talk might be worth upgrading to a tutorial for 3 hours (given enough people might be interested in going).
I didn't really get the idea of the talk. Was missing a bit of cohesion and goal. Missing a goal during the talk is fine, as long in the end the path becomes clear. To me it didn't.
Had some funny elements and the presentation itself was fine.
I did not leave inspired and enthusiastic, which is what I would expect from a keynote.
I'm a strong advocate of testing, however I agree completely with the speaker that sometimes testing, or certainly automated testing, is not worth the effort.
I think maybe examples or stories would have helped. E.g. in situation X I did a lot of testing and it didn't pay off because of Y. However on project Z we didn't do any testing and all these bad things happened.
From a technical perspective I'm blown away; that was one slick presentation.
Spending a few days digesting the talk I broadly agree with the take aways - you make your own luck.
It felt quite a bold talk, although there is context I'm a Brit and we're a bit more reserved and generally self deprecating. I'd find it hard to go on stage and say things like I think I'm better at X than person Y so I think I should be doing X. However this is an important reminder that there are subtle cultural differences and I should be aware that being more forward about ability might be required in different parts of the world.
To make it a 5 star talk I would probably make it a little shorter and focus a bit more on some of the detail. For example the speaker mentioned things like when in new situations work out the key players. Maybe a little detail on how to do that would be good.
Really enjoyable talk. Concepts well explained. Good slides clear slides.
My only tip for improvement...
I still felt at the end a little unsure how to actually read top to work out what was going on memory wise. I would have liked a final review of the top command output, maybe explicitly highlighting parts of it, as a reminder the the important information with regard to memory usage.
Great talk.
A great talk. Static analysis has come along a long way with PHP 7 and the message about these tools needs to get out.
Nice code ideas to show to write code in such a way to get the most out of testing and SA. I'll be making a few changes to how I code based on this talk.
Very nice talk, good content, summed it up perfectly.
Great content, well presented, and a LOT of information in 45 minutes!
Good to see another take on generating APIs documentation. I'm used to things like Nelmio.
I think missing from at the the start was a brief overview of how other tools approach the problem and why the need for the approach you outlined.
For example other API documentation tools that I have used use the annotations to get this information. If the annotations are also used to generate the routes then it is likely that the documentation generated will be correct.
The approach of returning an array with this information can leave the actual and documentation out of sync with each other. I spent a lot of the first half of the talk wondering why annotations were not being used. A little bit at the start explaining what is missing from existing solutions would probably have helped me,
As an aside: I see benefits for the method of API documentation generation you mention in fact I wonder if a hybrid approach would work best. Getting as much routing, parameters and return type information from annotations or router information, code reflection, etc and add the ability to override or add additional information via code (as your tool does)?
Interesting to see different ways of working. Thanks for the talk.