Re:Twitter’s poor API documentation practices
by mattdeboard on Tuesday January 10, 2012 @04:09AM
(#3446274)
"Well, we got a string instead of an integer and yada yada yada, our network almost collapsed."
That's a pretty big "yada yada yada" you left out. I am going to assume there's a legit reason why getting a string back instead of another type of reason crippled your servers, but I'd like to know what it was.
That's a pretty big "yada yada yada" you left out. I am going to assume there's a legit reason why getting a string back instead of another type of reason crippled your servers, but I'd like to know what it was.