tberman

NFL | Culver City, CA

The NFL (http://www.nfl.com) is looking for great software engineers to help build out its fan facing web, mobile and backend services. The NFL properties see hundreds of millions of users worldwide and its mobile applications are installed on tens of millions of devices.

We are primarily hiring iOS, Android, Web and Backend engineers (with a lean to people with an interest in full stack development). Currently we are building (and rebuilding) a lot of our core architecture. Our new iOS app is written entirely in Swift, our Android application using RxAndroid and our new web platform is based on React.js. On the backend we are in the middle of rebuilding many of our services experimenting with different technologies generally with an eye on immutable data and functional programming. We are very comfortable relocating talented people to Los Angeles.

If you are interested, please email me at todd.berman@nfl.com

NFL | Culver City, CA

The NFL (http://www.nfl.com) is looking for great software engineers to help build out its fan facing web, mobile and backend services. The NFL properties see hundreds of millions of users worldwide and its mobile applications are installed on tens of millions of devices.

We are primarily hiring iOS, Android, Web and Backend engineers (with a bit of a lean to people with an interest in full stack development). Currently we are building (and rebuilding) a lot of our core architecture. Our new iOS app is written entirely in Swift, our Android application using RxAndroid and our new web platform is based on React.js. On the backend we are in the middle of rebuilding many of our services experimenting with different technologies generally with an eye on immutable data and functional programming.

If you are interested, please email me at todd.berman@nfl.com

NFL | Culver City, CA

The NFL (http://www.nfl.com) is looking for great software engineers to help build out its fan facing web, mobile and backend services. The NFL properties see hundreds of millions of users worldwide and its mobile applications are installed on tens of millions of devices.

We are primarily hiring iOS, Android, Web and Backend engineers (with a bit of a lean to people with an interest in full stack development). Currently we are building (and rebuilding) a lot of our core architecture. Our new iOS app is written entirely in Swift, our Android application using RxAndroid and our new web platform is based on React.js. On the backend we are in the middle of rebuilding many of our services experimenting with different technologies generally with an eye on immutable data and functional programming.

If you are interested, please email me at todd.berman@nfl.com

By the way, happy to relo from anywhere in the US.

NFL | Culver City, CA

The NFL (http://www.nfl.com) is looking for great software engineers to help build out its fan facing web, mobile and backend services. The NFL properties see hundreds of millions of users worldwide and its mobile applications are installed on tens of millions of devices.

We are primarily hiring iOS, Android, Web and Backend engineers (with a bit of a lean to people with an interest in full stack development). Currently we are building (and rebuilding) a lot of our core architecture. Our new iOS app is written entirely in Swift, our Android application using RxAndroid and our new web platform is based on React.js. On the backend we are in the middle of rebuilding a lot of our services experimenting with a lot of different technologies generally with an eye on immutable data and functional programming.

If you are interested, please email me at todd.berman@nfl.com

As the guy who wrote the first bits of the Rdio code in question, it seems worth mentioning that the part in question has nothing to do with Backbone, or Ember, or anything else. That code is a cleanup function on an object that helps to abstract HTML5 <audio> vs our Flash fallback.

No matter what framework you are using, if you are solving the problems that we are solving, you are going to end up with that code.

Now, that said, I agree that learning all of the frameworks out there is advantageous, but you can't assume that the code in the blog post is indicative of anything having to do with Backbone or any other framework.

Agreed that it is possible, but it sucks to implement for the developer, which is Ian's original point. Its absolutely possible to do it, but we felt it was suboptimal, and opted to do something else.

Given then, how would you map a search that returns multiple types?

As far as deleting songs "safely", what Ian means is that for any given playlist (of which a user has an unlimited number) any given song can be in it any number of times. So when you delete a song, we generally ask for song_id and index to make sure that a) the playlist hasn't mutated (much), and b) we are dropping the right song. The DELETE on /{trashbin uri}/{song id} doesn't provide 2 of the 3 required bits of information, and DELETE /playlist/{playlist id}/{song id}/{index} isn't very RESTful (imo).

How is it any more inaccurate than: http://www.flickr.com/services/api/request.rest.html