I was not expecting a rabbit hole that deep. Who underwrite that api for shipping?
Normally I describe bad APIs as looking like they were written by a committee of drunken orangutans.
This thing makes the output of a committee of drunken orangutans look like art.
I’ve been pulling my hair out with the totally unrelated but also awful Marketing Cloud (owned by Salesforce). This article made me feel better.
Have read this yet, but I’ll absolutely give a +1 for the “fuck marketing cloud” sentiment. It’s like Salesforce bought it, then gave up on it.
Had to contact support this week because (on top of an already infuriating week of marketing cloud bullcrap) an exit criteria in Journey Builder was firing when it shouldn’t. Basically amounted to a string comparison of A = B? But one was from Contact Data and the other from Journey Data. And you know what their response was? “Yeah… that won’t work, you have to do B = A”. I kid you not. What’s worse is that actually fixed it! What a joke of a platform. How shit do you have to be at coding to end up making a string comparison non-commutative? Like…I don’t even know how you’d screw up that badly accidentally. It’s a veritable kaleidoscope of shitty infuriating bugs.
Wtf did I just read? This is in another league of bad APIs.
Beautiful.
The API is bad, I get it. But the author also seems a little too aggressive with the “my way is the best way” attitude.
