php[tek] 2015
18 - 22 May 2015 at Sheraton Gateway Suites O’Hare

It was cool to see that there really probably "Is An API For That". I haven't ever before tried to build an app using (almost) only other APIs that I didn't build but it was really cool to see the approach. I am much more interested in learning about a few of the APIs and technologies that were shown (like graph dbs) that I haven't been exposed to.

As far as the application, it was really ambitious. There is a bit of "going into the weeds" in ZF2 that is probably pretty tough to get around for people who are not familiar with ZF2. I'm not sure of a way to fix that other than considering Matthew's suggestion of using less framework (like a micro). I think building individual tiny apps that only each use a single API would possibly get through more APIs but would probably not be as interesting.

I really enjoyed you presentation about vagrant and ansible. These tools are something I plan on using in the very near future. It was nice to have a very detailed explanation.

Cheers

Good overview of provisioning vagrant VMs using ansible.

great tutorial. ansible demystified. i wish we had a little more time in the tutorial to work through the ansible-galaxy stuff along with the presenter, but the information and demonstration was very rich regardless.

I agree that independent examples of API applications may be a better fit, especially to help with following along. Giving an overview of the service and associated docs, an example service call or two, and maybe giving an exercise that enables the audience to use what they've learned and go a bit further in exploring the API might be an ideal presentation flow for each service. There's nothing to stop you from describing how the individual services might fit together into a particular whole application as more of an aside rather than the focus of the presentation.

Well-organized, accessible and thorough overview of security issues and solutions.

Learned about some useful APIs and a decent overview of implementing APIs. I would have gotten more out of it if framework-agnostic code was used, and if the pace was a bit slower.

Question for those with feedback on the sample app - while (I thought) a novel approach, do you feel it would be better to explore some of these APIs on a individual basis?

A simple login example (not one tied to an overall application), a standalone use of a media conversion API, etc? Would that be a good way to remove the some of the heaviness?

Perhaps also make it easier to follow along / be hands on?

this tutorial was great. covered a lot of features. suggested helpful standards to follow while getting started. i'd recommend this tutorial to anyone.

I really enjoyed it! Had some difficulties getting things set up at the beginning but that was to be expected. Joe definitely knew what he was talking about and even though I was a total newcomer to Laravel I feel like I've got a good introduction to the framework and I'm looking forward to learning more.