I am new to PHP although I have been programming for over 30 years. This gave a really nice over view for structuring projects and code sets
Slides are posted for those who requested them.
Also, this was the video I couldn't get to play during the talk: https://youtu.be/ZZTwH8C5bjo
Engaging and clear. I appreciated the distinction between encoding and encryption. Demos worked smoothly. Some of the screens would have been difficult to read if I hadn't been in the front row. Maybe it would be good to move some of the key material from live into slides for that reason, or otherwise find a way to make the display more accessible.
Stephanie's presentation was a perfect capstone plenary that was able to appeal to the entire range of conference attendees. The combination of the sailing narrative, business anecdotes, and teamwork philosophy - a deceptively tricky set of elements to weave together - was done skillfully and with a lot of humor. I was thoroughly engaged with the talk and thought the mixture of entertainment and wisdom was a lovely ending to this event.
Ashley's presentation was a profound moment for me at this year's conference. Initially unsure if I should even attend this talk with the anxiety that surrounds negotiation in favor of a "safer", more technical talk, I came away from this talk hopeful that I too could be a more confident and courageous negotiator. The presentation was clear and hit upon so many important issues (gender pay inequality, the importance of ASKING, negotiating as if advocating for a loved one). Thank you, Ashley! (Could you please share your slides, so I can pump myself up before my next negotiation? Thank you!)
Vesna made a great argument for how to capture ideas and reflections that might otherwise fall through the cracks of the workaday world. I appreciated the concept of ending retrospectives not with solutions but with concrete steps forward and accountability for those steps in future meetings.
This was a great extended commentary on moving beyond petty debates on the relative speed of certain actions (e.g. echo vs. print) and how to deal with large scale slow downs using logging and advanced analytical tools. The use of a specific case study was very helpful in visualizing this process.
This was a standout presentation. Jordan's experience as an instructor and presenter was obvious in this organized, clearly scaffolded talk. The topic was also extremely applicable to the conference attendees as I heard others and myself reiterate that we'd used git but knew there was more to it. After attending this presentation I feel more comfortable with how git works as well as some of its more complex options. Thank you, Jordan! (Here's a very minor ticky tack negative comment, to satisfy your desire for honest feedback: You possibly could have glided over the 2 vs. 3 dot elipsis comment by offering to look it up and talk to the person later. However, I'm super glad you didn't let the presentation get bogged down by entertaining more comments on that tangential issue. Ha, I still found a way to complement you on the one very marginally negative aspect of your presentation!)
Dave made an excellent argument for a fail fast mentality in an established team coding environment. Rather than plodding through building possibly unwanted features on the one hand or making changes for changes sake, the fail fast mentality coupled with split testing to determine viability really encourages useful innovation. His presentation was inspirational and engaging.
This was an entertaining and thoughtfully organized presentation. Pearl and Abraham did a great job arguing for the use of web components. This talk really inspired me to learn to code in a modular and therefore more maintainable way.