Building an API with Rails
Location: Ballroom I Audience level: Novice
Building an API is tough and we want to discuss some of the decisions made by the Twitter, Github, 37signals, NY Times, and ThoughtBot while building and growing their APIs. Each panelist brings a wide variety of knowledge and problem sets they’ve solved. Here are some of the topics we will try to cover:
- Authentication (Http auth, tokens, OAuth)
- Response Format Support (JSON, XML, yaml)
- Versioning vs Non-versioning
- Scaling and Code Separation
- Security concerns
- Developer communication strategies and importance
- Documentation tools
Four Bean Soup
A notable achievement for Josh; he lead his development team to win the 2007 Rails Rumble competition for the development of TastyPlanner.
Josh is a Podcaster and Producer of WebPulp TV. Josh spends most days striving to write beautiful, elegant Ruby code and leading his projects to succes.
Joe works for ThoughtBot and has worked extensively on the Hoptoad API.
Jeremy works at 37signals and has worked on most APIs offered by their web services.
Marcel is an API developer @twitter. He has previous worked for 37signals.
Rick is a Ruby developer at @github. He’s also developed several APIs for @entp.
The New York Times
Derek works @nytimes and has worked on various APIs there, including the Open Congress API.
Comments on this page are now closed.