I loved this talk at php[tek] last May. I didn't go to this iteration, but I sent a bunch of people to it. Some great mind-blowing concepts for takeaway. :) Excellent presentation, well organized, compelling. I like the historical context, too.
This talk delivered all it promised. I like the idea of "good code smells" that he introduced -- that might be good as part of an alternate title for the talk, in fact. The presentation was well organized, with good slide pacing and good examples. A couple of the concepts that didn't have examples could have used some, like decomposing classes with too many member variables. Also I was hoping to hear a bit more about why no static classes or utility classes. There was a quick explanation about why not static, but I didn't catch why not utility.
We have been focusing on establishing cleaner coding standards at my workplace, and I got some good takeaways to share with my team. Jeremy made an excellent case that adhering to these standards of beauty is practical, because the code is easier to test and run metrics on. He went over a good selection of tools, some of which we already use and some of which I want to look into now.
I think there would have been demand for Q & A if the talk wasn't already running late into the 30-minute break between talks (because the first talks of the day got a late start) I had to run, or I definitely would have enjoyed some discussion!
Excellent talk, well organized, great slides. Ben, the book I mentioned to you is "Zen and the Art of Motorcycle Maintenance: An Inquiry Into Values" by Robert M. Pirsig. First published in 1974, this metaphysical novel has many aspects I think you'll find relevant -- it's one of my all-time favorite books!
I agree with the other commentors about the section on debugging tools -- somehow it felt out of place. There are passages in ZAMM that address that feeling, though, so read the book! :)
Some of the folks at the conference are a harder sell than me on the fundamental message of your talk, it seems. I think that the way to reach them might be by bolstering your presentation with scientific facts about the benefits of meditation, and about the whole body/mind/brain/cognition complex. I think that could provide the hard edge that the tools section might have meant for.
Excellent presentation, well organized, nice bits of humor. The slides were very thorough and helpful. The system of starting with moving from installation to easy use of Varnish when all is well to problems and how to handle them was very effective. The explanation of HTTP made it even easier to understand Varnish. Very clear and engaging. Thanks!
Very thoughtfully presented. Exciting to learn about PHPUnit from the author himself! Sebastian collected questions from the audience and managed to process them all. Great tips on testing legacy code with big, mysterious functions. Nice comparison of PHPUnit and PHPSpec. I appreciate how Sebastian speaks admiringly of other testing libraries, while still defending his own philosophy. Thanks!
Emily clearly is a topic expert. Was glad for the opportunity to learn from her.
People were asking about software tools to use instead of sticky notes to create story maps. I would suggest adding a brief section near the beginning coming out strong with an explanation of why these physical tools are superior to GUIs or other software solutions, rather than just something to make do with for now. Then reinforcing it now and then. Emily's explanation during Q&A of how sticky notes get better involvement from more people was excellent, intriguing and persuasive and just the sort of seemingly counterintuitive element that can take a talk to the next level.
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.
A fascinating analysis of how her team bridged the gap from a huge legacy application to modern code. I like the narrative approach Emily uses. It brings the concepts to life -- including the bumps and setbacks. Well organized and thorough.
Nic broadened my understanding of what it means for something have a "barrier." Accessibility matters to a lot more people and in a lot more ways than I had previously realized. He provided plenty of examples of what to do about it, as well as further avenues for investigation.