Extremely fluffy piece. 20% in and not one valuable piece of information
It would be better and respectful of the readers time to get to the point of the article rather than stuff the article with more words wasting the readers time.
When I come across articles which are needlessly long, I either skip them or I use a summarizer and leave the page.
There will always be clickbait elaborate content like this, (clickbait title, actual answer at the end of the article 90% of the time) but it just trains the reader to just scroll to the end of the article for the answer most of the time, achieving the opposite of what the article writer wants.
> The reason I know this is because I’ve built and maintained systems that handle close to 100,000 payments a day.
That's 1.16 payments per second.
(it could be 2 payments per ride or drivers get batched payouts but w/e).
There's obviously bigger payment platforms (eg Stripe or GPay / Apple Pay or Amazon) but not all of us work in payments either
Uber, by comparison:
'Trips during the quarter grew 21% YoY to 2.8 billion, or approximately 30 million trips per day on average.'
That would be about 350 payments per second if load was evenly distributed.
What? Your mind wasn't totally blown by the advice "Instead, the lesson should be this: to test your payment systems in sandbox for an amount of time that’s reasonable. And not a second more."? /s