surajgupta

Thank you for this! Was really fun to peek behind the curtain. I appreciated your honesty in the "Shortcuts make long delays" section. Learned a bunch from reading this post.

Could use some love on my feature request. I think it would be high impact and seems like a pretty obvious high value-add to the product.

Really cool use of WinRM!

Really appreciate the level of detail of this blog post. Thank you!

I love StackOverflow careers. They are expensive, but draw a quality crowd.

thank you!

I have found that job posting are enough. Of course, you should try to tap your network whenever you can, but in practice that will mean a much smaller pool of people who are both qualified and looking for a new position.

Ah! I didn't realize that. Here's the direct link: http://obeautifulcode.com/doc/Learn-REST.pdf

I think "horrible" is pretty strong and perhaps you meant a lighter shade of gray :-) It is unfortunate that this doesn't work on Pocket. Thanks for letting me know!

thanks, Peter! I slaved over words in that deck, so getting this kind of feedback makes it all worth it!

Here's the link to SlideShare: http://www.slideshare.net/OBeautifulCode/learn-rest

you can "save" the presentation locally

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. =)

Yeah, as I said in my blog post this is certainly text-heavy. The more appropriate format would have been a article, but I wanted an excuse to play with SlideShare. This deck could have be thinner with more visuals if it were accompanied by audio or video as in a proper talk. But I didn't have the time to do that, so I wanted the deck to be self-contained. Just think about it as a textual blog post in slide format.

I agree with everything you've said. I intentionally did not separate "protocol" from "binding" in this deck. I wanted to take more of a pragmatic approach and less of an academic approach. In practice, REST is most often implemented on HTTP. Because devs can relate to HTTP, I coupled protocol and binding to keep things simple.

Here's source code for the release on GitHub: https://github.com/SurajGupta/r-source

The R team maintains an SVN repo, but I prefer browsing source on GitHub

source: http://cran.r-project.org/src/base/R-2/R-2.15.3.tar.gz

or you can wait for it to be mirrored at a CRAN site