Last month I gave a lightning talk at the Ember.js NYC meetup. The talk was about designing your API based on what it was going to be used for by the users instead of designing it based on what is in the database. I think that this tactic can be really effective as it reduces the complexity of the front end code, which is where your users are and where you really want everything to revolve around their experience, not the intricacies of your data layer. With more and more complexity living in the front end through frameworks like Ember.js our design decisions need to be giving more weight to the front end than they used to.
Video and slides below:
Video:
Slides:
http://slid.es/andremalan/your-front-end-is-not-your-back-end/
http://slid.es/andremalan/your-front-end-is-not-your-back-end/embed
andremalan.com 
I see a lot of interesting content on your website. You
have to spend a lot of time writing, i know
how to save you a lot of time, there is a tool that creates unique, google friendly articles in couple of minutes, just type in google – laranita’s
free content source
I read a lot of interesting posts here. Probably you spend a lot of time writing,
i know how to save you a lot of time, there is an online tool
that creates readable, google friendly posts in minutes,
just type in google – laranitas free content source