3 ms·

I've been playing with Twilio recently, and it's certainly not the lean platform that it once apparently was. In the Java client SDK for example, I count 7 sepa

I've been playing with Twilio recently, and it's certainly not the lean platform that it once apparently was. In the Java client SDK for example, I count 7 separate Message classes. There are multiple APIs with overlapping functionality; you can send SMS and whatsapps several different ways each. The documentation is likewise byzantine and bloated. I get that scaling tech organizations is hard (Stripe is another company with abysmal bloat in their APIs) but jfc, get a competent chief architect who is opinionated, please, and aim towards coherency. If you launch a new API that's intended to replace older ones, then stop exposing the legacy APIs in the default SDK. (That said, better than MessageBird, who don't even have SDK support for the APIs they're promoting as the correct way; on the other hand, their documentation is markedly better than Twilio's).

rabiddmeese 3y ago
> If you launch a new API that's intended to replace older ones, then stop exposing the legacy APIs in the default SDK. They might want to alienate and break things for many of their existing clients who use the older APIs. Plenty of companies contract out dev work until they have a working product and keep it as is. They don't have devs on hand to update them if they deprecate older APIs leading to a completely broken app despite all the old functionalities being perfectly adequate for the task.