Hacker News new | past | comments | ask | show | jobs | submit login

The developer experience isn't even the worst of it. Try running some reliability testing. It's mind blowing how bad Tropo is and how many random hidden variables exist in their system.



Which is really sad when you consider the problem. API accepts SMS and inserts into database; workers take queue from database and action against SMS gateways (works in reverse for messages going the other way).

How can this be that difficult to do?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: