4/ I build this complicated app that communicates with Vast Third Party via three different APIs, a mix of XML, JSON, etc. Two of these APIs are outgoing / push (from my PoV), one is inbound. Three weeks ago Third Party pinged us and placed an order. We responded "ok".
-
-
15/ You can predict 99% of the problems that are going to happen, and plan ahead to mitigate them.
Show this thread -
16/ Counterpoint to
@FormerlyFormer 's "male strengths vs female strengths" threads: youth strengths vs elder strengthsShow this thread -
Show this thread
-
18/ BigCo responded. "I looked in our system; I see our message to you, placing the order. Problem at your end." ok, BigCo, can you tell me what order ID # we gave you, and what our message said specifically? "there was no order ID. Your response was 'error: no inventory' "pic.twitter.com/V9tkGlGvUp
Show this thread -
-
20/ wife responds to my email above ("Woman! Fetch my excruciator!")pic.twitter.com/mW7EwxYDpc
Show this thread -
21/ me: can you confirm that you ignore the message we send back to you, even if we specify a well defined error code, as documented in your API ? Bigco: <2000> words me: ok, so you do ignore the error code. Alright, I'll dig into the other API now.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.