Then again, the team was always notably helpful during hackathons, and their documentation is usually on point. Maybe they recognize this as a company strength, and they are harnessing it as a way to compete with the likes of AWS/Google Cloud.
Nobody I know is a Twilio engineer, but nearly every backend developer I've worked with has, or wants to use, Twilio. There's something old school phreaking about using a computer to control phone systems.
They seem to believe that the market is very broad, occasionally deep (Uber was ~10% of their usage), and super cool. They haven't gotten so big to discard their focus yet playful roots (their hackathon outreach is a great example; that's where I first learned the API).
- wired ethernet
- lots of guard code that reconnects failed calls
- customer is aware they will not get 5 9's or even 3 9's.
Typically using WebRTC means a significant cost savings, so it may or may not be worthwhile to build out the additional stuff needed to make it work.
Much like when you go into a website and know (unlike your average mother/grandfather) where to put your credit card or not because of the "feel", this gives me the feel of an awesome company.
[1] https://www.twilio.com/signal/2016/video/6Gjpnzch0sggKeey0yi...