A 20 minutes tutorial for Ruby beginners on using Ruby and the Github API to create Mad Libs out of your commit messages!
Reminder from part 1: In this tutorial we’ll build a game that interacts with the Twitter API and challenges users to match a given Tweet with its author. The game is called Following, and you can play the fully-built version of it here: http://followingapp.herokuapp.com.
One of our clients needed their web application to interface with two external APIs. Neither API had a native ruby gem that we could pull into the web app project. We decided to write our own gems, one for each API. The web app and the APIs all target the same domain, but don't use the same domain language. The subtle challenge was to figure out how to interface with these APIs without adding confusion to the web app's domain language. I'll talk though our story on how we came to a clean solution.
Both of the external APIs were from the same organization, but created at different times by different teams, and consequently looked a lot different from each other. What's worse, both APIs are concerned with the same core concepts and entities, but the APIs called the entities different names.
And.... it still gets worse.
- ← Previous
- Next →