Day Camp 4 Developers
7 Nov 2014
at Online
Talk comments
Tip after tip it was a great presentation highlighting things we often neglect, but are super important. and how to fix them.
I especially liked how each problem was followed by a number of fixes and real world examples.
The talk was informative and well presented, but to me it felt like it was more suited for non-developers.
This may be the first DC4D talk that I watched in real time and will rewatch later to make sure I interalize everything.
Well done, sir, well done.
Well presented, but didn't really seem appropriate for a conference aimed at developers interested in building APIs. I would assume (yeah, I know) that most of the developers attending this DC4D already know what an API is, want to build one or already have, and want to learn how to make better APIs.
This presentation give API designer/developer/architect/manager straight forward solutions to common pitfalls which are really easy to implement and will make the consuming developers love your API.
Really awesome presentation. Really enjoyed it and learn few things, no doubt it will have an impact on our API design and management decisions.
I work in an environment where team within the org or even the products from same team are always communicating via API. This presentation has highlighted area where we need to improve. So thank you John.
On the other parts we lead on things like monitoring of our API status on screen live in the office so we know how things are going even before people find out about an issue.
The presentation was at a speed that it was very easy to follow. Thank you Cal for organizing this event.
Enjoyed the talk. A lot of good points on how to make consumers of your APIs happy. Touched on many of my pet peeves. Something I didn't notice in this talk that we discussed a little on IRC was -- if you're going to have throttling limits on your API, include something like "retry_in:120" in the api responses to make it easier for your api consumers to write code that can recover from hitting API limits. Another thing I'd mention -- if you have a developer sandbox/playground where devs can paste their api key and other auth tokens, please save that stuff in a session var and repopulate the forms for your sandbox users so we don't have to re-copy-paste that stuff on every page refresh! That used to really irritate me with AmazonMWS.
Great talk, both the content and John were excellently presented. I'll be keeping these slides at hand when they are released!
Lots of great information. Thank you for all the examples. Would love to package this up and send it to a few developers as a not-so-subtle hint.
Great talk. Lots of interesting points.
Great talk and great slides. Slides could be used as a checklist.