That's dramatic. Learning any new topic, particularly one as involved as REST, require some investment of time. Your blog post has FAR more content than my slides do. And your approach is from a "best practices" point-of-view. So the arc of our stories is necessarily different. I'm glad that blogs enable people to learn the same topic in multiple ways. It's a good for everyone. I just wish people would avoid self-promotion on top of other people's backs. =)
I have found the article I linked to be incredibly digestible for people learning REST, which is why I recommend it; regardless of the point-of-view. It's what I think is missing from your slides. You might be able to solve this in the context of an actual presentation, but taken as just the slides, it's very dense.
Also, this isn't self-promotion at all. I'm not in any way associated with that blog. I just like the content.
Different perspectives and learning styles, I suppose. I'm not trying to be argumentative, just briefly laying out my thoughts. Cheers
For anyone interested, this is the article I hand out when someone asks me about designing a REST API: http://www.vinaysahni.com/best-practices-for-a-pragmatic-res...
And here is the HN discussion from when it was originally posted: https://qht.co/item?id=5819231