Gems sometimes make it harder to work with APIs

Yea, fuck. For instance there’s the twitter gem. It’s not created by Twitter. It’s created by some random guy sferik who failed to write any documentation for his gem.

Compare that to the twilio gem for the twilio api. That’s maintained by the people over by twilio so it makes sense to use that gem. But the twitter one, not really so much.

It’s important to not “NEED” a gem work with a given public api. It’s great when it’s possible to make requests and consume the api without relying on some other slouch to make it all possible for you. I wish I could write you some code to help ya out with this, but I ain’t gonna. THANKS LATA CHOW i mean ciao..

Post Content