The Stripe API now makes suggestions in response to misspellings!pic.twitter.com/152wU4LPqY
-
-
Replying to @patrickc
Asking this as a curious outsider who knows very little about software. Why is this a recent innovation? Auto-correct seems like an obvious problem the software community should have solved years ago. Perhaps there's a lot of technical complexity here. What am I missing?
8 replies 0 retweets 15 likes -
Replying to @david_perell @patrickc
A true but perhaps unhelpful answer: it doesn’t exist in most APIs because no one implemented it. A perhaps more useful answer: broadly speaking, most APIs are bespoke software systems. This layer is built from ground up, rather than being built on a common, robust foundation.
2 replies 4 retweets 39 likes -
In contrast, when you’re using an operating system or a programming language, you get to benefit from a lot of work done over years or decades by others. (Whether they have great ergonomics even given that advantage is... a very mixed bag.)
1 reply 1 retweet 5 likes -
Why don’t engineering teams in industry prioritize implementing e.g. better error messages? A combination of undervaluation of the end-user developer experience, competing priorities which product teams thought were more important, and belief that bugs are user’s responsibility.
2 replies 2 retweets 9 likes -
(At risk of stating the obvious, every team/colony/professional has a different level of agreement with these, but let’s say that these are the defaults you get and anything on top of that is a result of you deciding to make it happen.)
1 reply 2 retweets 5 likes
*company (This which might be one interesting example of a reason why APIs don’t simply assume they know what an engineer meant when typing something a short distance away from a valid parameter name.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.