Ryan’s wife: Why can’t a machine understand a normal web page?
Ryan: Because web pages are designed to be understood by people. A machine doesn’t care about layout and styling. Machines basically just need the data. Ideally, every URL would have a human readable and a machine readable representation. When a machine GETs the resource, it will ask for the machine readable one. When a browser GETs a resource for a human, it will ask for the human readable one.
– Ryan Tomayko: How I Explained REST to My Wife
(I highly recommend reading the above article, it’s a nice introduction as to what will follow this week.)
Firstly, he suggests we learn Handlebars – which you should have been introduced to back in March – Week 4, so go learn Handlebars. Then we move on to learning Backbone.js. Here’s my thoughts:
- – Having worked with and PHP and WordPress, we have already seen some back-end development. However what struck me is that it’s quite tough to imagine myself creating anything independently, but I feel I’ve come far enough now to just keep tooling away at it. The 2 key resources here for me were Thomas Davis’s site and accompanying video – which I think you should watch first (I always prefer videos to soften the landing) and Addy Osmani’s book which is kindly availible for free (but I think I’ll be buying a copy in the future).
I’m currently still working my way through the curriculum, and I’ll likely put it on hold for a while as I have some other projects I’ll be working on. Hope to be back working with it soon, if you want more I’d take a look at Codeschool, I’ve heard good things and they’ve got their own backbone course.
1. Go learn Handlebars.
2. Then move on to learning Backbone.js