The structure and code samples were great--clear progression, and the code was readable and easy to understand. I left wanting to replace all my native PHPUnit mocks with Mockery.
Mental health in the workplace is an important subject that needs to talk about more. Finkler did a good job presenting on it.
Brave to do that large of a live demo but it went smooth (and you said you had slides just in case). Excellent details on how to profile and optimize sites. Good charts and details shown to make point.
Great talk, really was geared at some simple basics. Never strayed into the black hole of when and what to index, as that topic can be subjective at times and is rarely concrete. Still, it was touched on indexes with some good "rule of thumb" ideas to consider.
Awesome talk, constantly enforcing the idea of baby steps are better than nothing and trying to make leaps when changing code will likely hurt you was encouraging to hear.
It's always helpful to see not just what can go wrong but different methods to mitigate or prevent the attacks. Hearing that there are some threats you'll just have to accept unless the feature has to be changed or removed was helpful. Trying to get managers to understand that concept can be difficult at times.
It was great to hear not only options on caching, but the very dangerous pitfalls of various methodologies.
I took some of his ideas and tried to implement them at work. A small change with a large impact was enforcing the rule that every pull request is required to have a junior developer be one of the reviewers, the other being a senior developer.
This gave us all the opportunity to mentor the junior as a team. The junior gets to see where in the code base a feature change would impact, then see the "right way" (according to project standards) to implement the feature change. Bit sized chunks of new information that they can then turn around and use immediately. I've seen some juniors on my team improve their workflow by leaps and bounds both in the way they think through problems and how they choose to solve them.
Learned a lot about mental health for developers. Ed did a great job sharing his experiences and explaining why this topic is so important. Loved his survey comparisons between mental and physical health. Ed kept a good pace and had plenty of material to cover during the presentation. While he did run out of time he was able to make the important points that he needed to make. Well done!
Good values that allow you to avoid mistakes.