PNWPHP 2016
15 - 17 Sep 2016 at Cornish Playhouse @ Seattle Center

Excellent examples of when to improve and how to improve our code, and thank you for the coding in live!

Currently I am doing the same thing with my company I have more challenges than this because we are migrating from a pretty old version, so more changes in the code is required, however the way it was described was perfect to check if I am missing something for the migration process. Thank you!

Honestly, the way that Graham explained the monolith systems and how to move forward with micro services was incredible clear, also an excellent share of resources where we can start from.

Sadly, it was not what I expected. Taylor took around 10-15 talking about himself instead of talking about Laravel and important pieces of this framework. We have many powerful tools and things around laravel and I expected to see that instead of a life description of Taylor.

Thanks for kudos Adrian & Ian ... Ian as to your feedback on the %'s ... I actually agree with you. I think that the percent of 'PHP coders' who aren't part of the community, who are in the '3rd ring' is probably something like 80 or 90% (or higher). But if I said that in my talk, IMO, people would have taken me to task because I don't really have real numbers to back it up.

So I decided that it was best to 'way underestimate' at 50%, because few would actually argue against that number. And as you said, if I'm low (which I believe I am), it makes the call to action all that more urgent.

Well-delivered and informative on three different databases with three different use cases, making me rethink my MySQL monoculture just a bit (okay, I'm a big Redis fan, so no new news there :) ). Fit well with the graph database talk earlier to help break folks out of the M part of the LAMP stack, which is particularly valuable given various machinations around MySQL these days (though, hey, 5.7 is pretty cool!).

One nitpick: no one uses MySQL 5.7.0 to my knowledge; I think 5.7.9 was the first real production release, and 5.7.11+ is what's common. Would love to see the next edition of this talk using a current MySQl 5.7 release up against Postgres performance wise. My guess is that MySQL wins in a few more areas, but not to the point that Postgres' quality of life improvements aren't worth pursuing for a greenfield project.

Solid talk, with a clear call to action. Though I think that the fraction of folks who aren't currently in the community is waaaay higher than he estimated during the presentation. But hey, that makes the call to action all the more urgent.

Solid presentation, solid live coding. Didn't capture my attention too much as I've done some of the Refactoring To Collections tutorials before as part of a previous local meetup, but sounds like things were eye-opening for many attendees, and it's good that folks now have a tool for more fluent, maintainable code going forward.

As an aside, while the closure-and-collection method of dealing with stuff *is* slower than for loops everywhere, for data sets that aren't in the thousands (or hundreds of thousands, depending on complexity), you're not gonna care. This is by someone who should be in Micro-Optimizers Anonymous :p

Solid talk detailing experiences of what and what not to do when building communities. Not a position I'm in at the moment...maybe I'll get to work on some fun platform project at a later point...but still quite interesting, war stories included.

Loved the gasp across the room when Will showed the before-and-after RAM/CPU graphs for Etsy pre- and post-PHP 7. As someone who has pushed for PHP 7 upgrades for a few different clients (with a fair amount of success), it's great to hear a detailed case study on how a big, complex, heavily PHP-dependent company made the switch. Particularly great given that they were able to compare against HHVM at times, weighing the pros and cons of both new architectures (something I've done myself...and settled on PHP 7 as well).