haikuginger

18 ms·

1. 181.▲
   Why working with REST APIs sucks, and a case for how it doesn't have to(beekeeper.readthedocs.org)

   2 points by haikuginger 10y ago|0 comments
2. 182.▲
   by haikuginger 11y ago

   >Toad reviewed his team’s backlog and marked 80% of the open tickets as CRITICAL or BLOCKER. Ouch.
3. 183.▲
   by haikuginger 11y ago

   This is a shameless plug, so I'll take my beating if it's appropriate. For the last few months, I've been working on a Python library, beekeeper, that's all about that. It essentially consumes a JSON description file tha
4. 184.▲
   by haikuginger 11y ago

   I don't think that's necessarily the case - I think that if Apple switched architectures now, there would be a lot fewer issues than there were with the Intel switch. Over the past few years, Apple's done a lot of work in mak
5. 185.▲
   by haikuginger 11y ago

   I'm Jesse - the creator of beekeeper. The idea is that actually writing code to work with REST APIs kinda sucks a little bit. And doesn't usually give you a very good native structure to work with. beekeeper aims to change that by
6. 186.▲
   Show HN: Beekeeper: a codeless object-oriented REST API client library(github.com)

   3 points by haikuginger 11y ago|1 comments