whining about SDKs 

OK, bad enough that they have separate SDKs for the separate APIs for the two different steps in this process that are almost always going to be run in sequence.

But why, WHY, when the APIs both include certain common features that should be the same in both steps, would the two SDKs use completely different terminology in the methods used to build that feature? I can't just build it once? I can't even copy-and-paste it?

whining about SDKs 

I suspect the teams who built these SDKs - which are, again, for two steps of a two-step process - went off and did their own thing without any sort of coordination - no plan, no discussion, maybe they didn't even say hi to each other in the hallway.

TBH, I half-suspect the same of the teams who built the APIs they connect to.

Show thread

whining about SDKs 

It's like...if in order to post a photo with a caption, you had to post the photo to Instagram and the caption to Twitter and make sure the tags and usernames and timestamps matched properly to get them to show up together.

Show thread
Follow

whining about SDKs 

And yeah, you used to have to do that - when Twitter and image hosts were entirely different services. Even then, all you really needed to do was link from one to the other. You didn't have to repeat half the information in a new structure (but get it exactly the same) - and you could justify it because they really were two different services, not two steps of the same process.

Sign in to participate in the conversation
Wandering Shop

The Wandering Shop is a Mastodon instance initially geared for the science fiction and fantasy community but open to anyone. We want our 'local' timeline to have the feel of a coffee shop at a good convention: tables full of friendly conversation on a wide variety of topics. We welcome everyone who wants to participate, so long as you're willing to abide by our code of conduct.