Midwest PHP 2016
4 - 5 Mar 2016 at Hilton Minneapolis

I enjoyed some of the analogies to what society is doing now that are causing this rift, the toys and the expectations we have for girls and boys. I sincerely hope that this talk gets out and people stop gender labeling such things.

Thanks for being brave and getting up in front of a bunch of people.

I can tell you have a well of opinions and experience and that is awesome. I have to say I didn't get the connection between the SOLID principles and the rest of your talk. I would recommend stringing the principles throughout the talk to hit home each point with the examples of explaining the clean architecture. Also, more examples.

Also, it was kind of hard to hear you because of the lapel mic.

Cool stuff, Larry. Thanks for putting this together.

This was a great talk, Joe. I like the quick start git repo that I can take away with this talk to explore more.

I would recommend talking about the sample site first before diving into the code (what is the purpose of the site, how would users interact with it, what is it trying to achieve) so I would know what I am looking at at each step of the way in the code.

Thank you, Kayla, for standing up and teaching me something

You can find my slides here: https://www.dropbox.com/s/34zg3tutx7xjov1/HLWIT_MidwestPHP2016.pdf?dl=0

There were three key takeaways I appreciate getting from this talk:
1. Spend lots of time upfront identifying a well-designed API.
2. Abstract your API from the implementation at all costs, even if your implementation is currently an API provided by an external vendor, so that swapping out the implementation in future doesn't seem an unapproachable proposition with respect to enterprise continuity.
3. SOAP with WSDL's problem is how likely it is for the level of detail implied by a WSDL to make you de-facto coupled to the specific implementation of the service that generated it.

I had a hard time following the benefit of splitting the Experience layer and Process layer in your three tier model. Just a little more explanation of that would have been helpful for me.

In conjunction with other talks about microservices, the longevities of apis, and the options available for classes, interfaces, and traits, this talk provided code examples along with theory (clean) for amending the practices of the semi-pro php coder and taking them to the professional level. It is natural that some of the changes is my own coding remain mysterious to me, however in testing i will know when i've succeeded. For the amatuer the talk may remain obscure, and for the professional trivial, but to bridge the gap is a difficult and instructive step.

This felt a little rushed. It was a good overview of the tools, but I don't know that I could walk away from this and do much with the information I got out of it. It might be too much to cover in one talk, maybe narrowing it down to just one of these tools would be more helpful.

Speaker quality on this was great. I think it was a really practical approach to the problem. But this is a difficult topic, and this talk had some large pieces missing. This talk felt like it was approached from a third-party contractor angle with big design up-front, and left out some of the long term strategies for estimating. Things like velocity, takt time, and cycle time weren't covered well. That said, it's a huge and difficult topic, and I think, overall, it was delivered reasonably well.