anchor.diff:  
   ### Let's Paginate
   
  -Trello provides endpoints for traversing actions taken on boards, cards, and lists. We'll add an alternative method to `get` that can handle pagination.
  +Now we'll add an alternative method to `get` that can handle pagination.
   
   ```ruby
   def paginated_get(path, options = {})
     params  = options.dup
     max     = params.delete(:max) { 1000 }
     page    = params.delete(:page) { 1 }
  +  limit   = params.fetch(:limit) { 50 }
     results = []
   
     loop do
  
positive.code:   - Ruby
  ---
  
  When we need to retrieve lots of data from an API, we typically end up dealing with paginated data.
  This is because there may be limits placed on the amount of data we can retrieve in a single request;
  we can't get it all at once.
  
  The thing with pages is, handling pages in our get __messy__.
  
  You may want know how many Trello cards you marked as completed each month since last January, but you
  don't __want to think about *pages*__. <img src="<%= image_path('icons/noun_63447.png') %>" class="icon-image inline" /> <img src="<%= image_path('icons/noun_63453.png') %>" class="icon-image inline" />
  
  
  There are a number of Trello endpoints that return collections of data, such as boards, lists,
  cards, member, and actions like comments, copies, moves, etc. In some cases, Trello will provide a
  default limit, typically 50, on the number of resources returned in a single request. To get more
  data, we would need to provide additional __paginated__ requests.
  
  Let's take a look at how we'll do this.
  
  ### Trello World
  
  First, some plumbing. The [Trello developer docs](https://developers.trello.com/) have some helpful information to get started quickly in javascript - here's the unofficial Ruby version.
  
  While logged into your Trello account (you'll need one first), visit the [App Key page](https://trello.com/app-key) to retrieve your app **key**. We won't need the "secret" for this article.
  
  
negative.code: 
  ### A cursor-y example
  
  Let's do one more iteration on our `#paginated_get` refactoring. Up to this point, we've been using a "functional" approach; we've just been using a bunch of methods defined in the outermost lexical scope.
  
  First, we'll extract a `Client` responsible for sending requests to the Trello API and parsing the responses as JSON.
  
  