php[world] 2015
16 - 20 Nov 2015 at Sheraton Premiere

Thank you, Samantha, for a very...moving talk. You're an amazing speaker.

Cal,

Im in the in-between of lead, senior developer and manager at the company I started several years ago. I've struggled to create a great developer culture, and my President/CEO isn't helping any.. it's really up to me.

Your talk was inspirational to me. I downloaded your book (that you SO much!) and I'm already half way through it! I look forward to implementing some of the strategies you describe and checking back in 6 months from now to share my experiences trying out your methodology in my own little fish bowl.

Thank you *so much* for stepping in for this talk when the original speaker couldn't; most valuable talk I've been to at any conference... pretty good considering you didn't think you even had 10 minutes of content. You nailed it.

Decent introduction to the topic. Definitely got me thinking about the topic for my own system, and I really appreciated the effort. Live Demos are always scary, and rarely work as intended :-)

From the sound of most in the room, a diagram that showed *when* the IDS should do its work seemed to be in order...

Something like.. Without an IDS a system generally works like this:

User Submits Form > Validate Input on the Front End > Post to the backend > Validate Input on the Back End > Push Content to the Database.

*WITH* an IDS, it would look like this:

User Submits Form > Validate Input on the Front End > Post to the backend > IDS check the input >> If it passes (below a certain threat level) > Validate Input on the Back End > Push Content to the Database >> Else > Log, Email, etc. > Redirect User to "Server Error" page.

Obviously, you could build a much more effective flow chart then my scriblings above, but I think you get the picture.

Only other comment, the slide regarding the Apache log was an interesting exercise.. except.. everyones Apache logs are different. So, first I had to figure out what all the fields were that you were displaying (HTTP Code, size of return, route, etc.) and then try and think about what the site structure might be.. and then analyze the log.

Maybe update that slide to be more.. table .. like? With some headers, so we can easily see what each piece is? And then.. split them into a few different definitive examples that you want to show. It felt like.. we were guessing what the problems were.. and you were spit balling what the problems were too. It was a good exercise, just didn't feel .. instructive, I guess.

I think your public speaking skills are good, and you represented yourself and your company well; so good job overall, just a few things I picked out. :-)

Material presented so that I might actually want to do more work in Drupal. At times a little hard to hear from the center of the room. Might have needed to turn up the mic a bit.

This was a good presentation on using the tools available in D8 and the Devel module. These new tools are a welcome improvement over D7.

Very good talk! One of my favorites of this conference. Lots of great ideas and things I can go home and work on.

As always very thorough and well informed. I learned a ton.

A great in-depth talk on caching, it's history, theories, and implementations.