Talk comments

Anonymous at 23:47 on 7 May 2015

First half of the talk was good, with some concrete suggestions that developers on any platform could benefit from. Second half dove into specifics on PHP which was not mentioned at all in the description of the session. I would have preferred a higher-level presentation of toolsets across multiple languages instead of PHP-only examples.

Anonymous at 23:47 on 7 May 2015

First half of the talk was good, with some concrete suggestions that developers on any platform could benefit from. Second half dove into specifics on PHP which was not mentioned at all in the description of the session. I would have preferred a higher-level presentation of toolsets across multiple languages instead of PHP-only examples.

Phil,

You are correct, you did talk about image uploads and I believe the point was the body of the PUT would be the image data or the base64 encoded image data depending on how you build it. The question you answered at the end did touch on hypermedia, I was just hoping for a bit more since we are using it in our APIs. And you did talk about OAuth and show a sample request of logging in via facebook and talk about that you could do a facial recognition grant type which did sound good. For that I appreciate it. I think my gap in understanding is more on what, if I'm auth-ing via third party, do I need to store or keep track of on my side to make sure that the user is able to do what they should be able to do, etc. I think there's probably a very simple explanation that I've been missing in various oauth talks and things I've see that I was hoping I'd see here.

In any case, it was a very good talk and very enjoyable. Thank you very much. I'll see if I can't bump the rating up.

David

Thanks for the feedback!

This talk was in the Architecture track so it was intended to be applicable to any programming language or IT project. I will add some concrete examples of possible technical debt items for future presentations, good point.

The personal financial debt references were intended to help relate to the impacts and solutions to technical debt.

The discussion regarding technical tools and practices like continuous integration servers, unit testing, abstraction, interfaces, inheritance, static code analysis, and configuration management tools was intended to give direction on analyzing and addressing technical debt within a project.

Thanks again for the feedback.

Anonymous at 21:52 on 7 May 2015

This was really interesting until it took a turn into PHP. Next time skip the language specific tools or make it very clear in the description that it is a language specific class.

Anonymous at 21:50 on 7 May 2015

Very informative. You are clearly knowledgable on the topic. Will you post your slides?

Anonymous at 21:48 on 7 May 2015

Great job Cam. Way to keep it cool with so many demos in the hopper! I think the number of projects you attempted to demo in one hour was a bit ambitious. Even so, you managed to display some cool stuff even though it didn't go perfectly. Well done.

Anonymous at 21:46 on 7 May 2015

Stellar talk. Exciting speaker. Thanks for coming!

Anonymous at 21:44 on 7 May 2015

Great talk, very thought provoking. It's great to an approach to a problem that many of us are facing.

Anonymous at 21:42 on 7 May 2015

Great topic, not enough meat, details, examples, etc.