OpenWest 2015
6 - 9 May 2015 at Utah Valley University

Hey David,

Sorry you didn't think I covered those bits. I talked about image uploads towards the start, which is of course the same for any sort of file and I talked about OAuth for about 10-20% of the talk.

HATEOAS (a.k.a Hypermedia) was covered in the questions at the end, but yeah I cut it from my talk is its not the most important thing for people when they're learning to API. It's useful for building long lasting APIs that are counted in decades not years or months, but most of us don't do that, and by the time we are, we know how to add a link to stuff. :)

Thanks for the feedback!

Given the downloadable examples this presentation hit the spot. It was rich with examples - almost over abundant. It was fast paced, which would make for difficult consumption but with the downloadable examples it was safe to move so quickly.

Very basic overview that glossed over any pain points and was done in 20 minutes. Needed real-world examples and better discussion of cron analogues in a queue-based system (e.g. scheduler, delayed jobs). What is cron really? How can a queue provide this?

Loved the sample code, and the practical application!

It would be great to have more concrete examples and tools and how to's. It would have been great to see some technical debt dashboards, sonar examples, etc.

Good talk. Thanks for making git repositories something that is tangible by providing a mental link from commits to nodes.

Too long time explaining the problem.

Concrete example of a piece of technical debt or something that needed to change would be helpful.
I think that the biggest source of technical debt is 1) we spend reasonable time to architect some software, and then we 2) code it, and then we find out later there was a different way we could have done it or the new requirements are not amenable to what we originally wrote.

This lecture was very abstract.
Simply saying that there is a comparison between personal finances and technical debt does not seem to actionable.

Again to simply say "make your code less complex" is very abstract.

When it came to best practices "attend a local user group" was a good example of an actionable helpful comment, rather than "find the best practices and use them."

Very entertaining and informative. I don't think it covered all the things in the outline (like sane file updates, HATEOAS or OAuth) but it was a good talk.

Here is a link to the slides from the presentation: https://docs.google.com/presentation/d/1eT5nM98VTQPJ34dAKU6Fcw7dh1X61C-T1qOJSqIZ2Pk/edit?usp=sharing

There is also a link on the questions slide to the files from the live demo.

Very good sampling of real-life, experience-gained insights. I just found myself alternating between nodding in agreement and taking notes.