Great talk, I love those kinds of talks where people talk about something they're really passionate about.
It's great to see that Derick still has many good ideas and visions for XDebug, even after so many years. I fully agree that DX (Developer Experience) and better Usability is a very important point.
Thanks for the talk, nothing to improve! :-)
Very enjoyable history of the 'definitive solutions' that we, as old developers, have seen in those 25 years of PHP.
The current definitive solution? Using curried functions to meet the functional paradigm.
Very well presented :-)
Thank you for this talk, it was interesting to see some other CI / CD workflow.
Maybe some more abstract information would be good, e.g. an overview or pros / cons of different tools.
Nice insight.
Hi Francesca,
Thank you for the feedback, I'll invest some extra time to focus on verbosity during demo, I wasn't aware it was that bad.
I usually don't do live demos in my talks but wanted to show how easy it is to use both libraries together, would it be better if I dropped the demo completely?
Great insights that help appreciate the elegance of simplicity!
Encouraging talk for everyone to get more involved. :-)
Could have maybe emphasised a little bit more about getting involved in Open Source and with more examples, e.g. possible also to work on docs (most devs hate that!), translating stuff like interface, creating issues (was mentioned shortly), manual testing, etc.
I'll still give it a 5, as it was a great and encouraging talk.
Informative and great talk. Especially the beginning was funny. Good overview of how developing in PHP changed.
Thank you.
I'd like to suggest more verbosity during the demo in order to help the audience follow what's going on and keep them focused.
First of all thanks for the talk.
Personally, I didn't have new insights from the talk and the description "This talk is aimed at those who already write tests and have a good understanding of SOLID principles." sounded more like the talk is targets people on a higher skill level (already test experienced).
The things mentioned basically break down to treat your test code the same way you would treat your application code base. Apply code decoupling also there, structure them into own classes, methods (e.g. Page Objects were mentioned) and re-use test code as well. For me, it would have been great if some more / other principles had been shown. Behat for example could have been mentioned, also "UI Testing" doesn't have to involve UI at all (that was slightly mentioned), but instead could just be API testing (send a Request, validate the Response).