Lemon is an engaging and charismatic speaker. I really learned a lot for the short timeframe. The examples were trivial and thus a lot of the complexities of an actual *app* were skipped over, but he gave pointers to where to go next for that info. For a one-hour talk, it was great.
Great topic, and Chris often quite hilarious. A good perspective for us all to keep in mind, and I agreed with pretty much everything Chris said. Rather repetitive though, and the "Guide" ultimately came down to two bullet point suggestions. I would have appreciated just a little less time on commentary and a little more time on how an AI-skeptical dev can engage with LLMs ethically.
Thank you for the talk. This has given me a lot to think about as I onboard new developers onto our team. I'm still trying to work out the "onboarding" process even after a decade of doing this and there were a lot of good nuggets of information in your talk (I was especially happy to hear I wasn't doing it completely wrong :-)).
Thank you for the talk. I went to this because Alena said it was really good and I agree. I think some of the examples were a little hard to follow because you had multiple screenshots to look at and it was a little overwhelming.
We use Regex all the time at work but there were a lot of little pieces in your talk I didn't know or had forgotten about. I'm still not sure when I might use a Lookaround but I have that tool in my toolbox now. :-)
Thank you for the talk. I came into this talk expecting more of a "here's how to organize your code in a monolith so it's easier to maintain" discussion. I'm not sure I still wouldn't think that from the description.
That being said, when the concept finally sank in it was really eye-opening. I already have plans on how we can us this pattern in our main application (which will be 6 applications in the future :-)).
This was a great overview on what you can currently do with AI in your daily code workflow. I appreciate all of the resources you shared with us, and the hackathon was really fun. I can't believe the games that the groups made in 45 minutes with the help of AI, that was such a great idea. Another attendant and I remarked how quickly the time went by, I can't imagine how much cooler the games would have become with another hour or so of dev time.
Solid info, got some great ideas from the section on triggers. Really appreciated the emphasis on showing actual code. If this were a longer talk you could add some more depth on backup strategies and architectural issues like replication and non-prod instances (or not, and just recommend something like Planetscale). All in all though, excellent talk.
Fantastic talk, Kaitlyn is clearly one of those people we can all be glad is on our side. I particularly liked the discussion about non-obvious accessibility issues such as "wall of text". The AI section went a bit long and seemed a little tangential at times, but on the other hand there were some solid suggestions for how to use AI effectively in an equity-minded context.
Very clever and insightful approach to understanding what is coming in PHP. I particularly appreciated the resources survey, and outline of where to get what info and how to understand it. I did wish he had spent less time on historical description and on scrolling down the RFC vote tables and a little more time actually reading what was there, and extrapolating that to a prediction of what would be in v9. The talk title did suggest more of a forward looking perspective. He did that a little, but I felt like that could more of an emphasis.
I appreciated the concept of splitting systems into different components, particularly the idea of a dedicated "service" for authentication. From my understanding, the approach here suggested setting up multiple, likely full-stack, applications alongside each other. However, with modern frameworks like Symfony, I wonder how large an app must be to justify this structure and what the specific trade-offs are. Also, how can we ensure a cohesive front-end experience across separate applications? Is the aim essentially to build internal APIs? Overall, I enjoyed the talk, but I felt it stayed somewhat at the surface level.