5 ms·

Extremely fluffy piece. 20% in and not one valuable piece of information

by jatins 2y ago

rty32 2y ago
Whenever I see an article with more than a few sentences that seem to be arbitrarily bolded, I know it isn't worth reading. Haven't had a failed case so far.
- dartos 2y ago
  How would you know if you did?
  - amne 2y ago
    you read HN comments and confirm that you did well to skip the rtfa part
colesantiago 2y ago
I'm beginning to think that Substack the new Medium, and this cannot and will never be solved. 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.
red2awn 2y ago
Stopped reading after this > 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.
- djtango 2y ago
  1 payment per second. 1 payment per uber ride. 10 dollars per ride. 864k per day. 365M per year. It's not a small system and could be some mixture of one market at Uber or some %age of rides (eg one payment provider) (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
  - deserted 2y ago
    The author works at Kiwi.com, and says there are '70,000 times a day a customer clicks the Pay button on our platform' which is a little under 1 QPS. 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.
tivert 2y ago
> Extremely fluffy piece. 20% in and not one valuable piece of information 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

Extremely fluffy piece. 20% in and not one valuable piece of information

by jatins 2y ago

Extremely fluffy piece. 20% in and not one valuable piece of information

Whenever I see an article with more than a few sentences that seem to be arbitrarily bolded, I know it isn't worth reading. Haven't had a failed case so far.

dartos 2y ago
How would you know if you did?
- amne 2y ago
  you read HN comments and confirm that you did well to skip the rtfa part

colesantiago 2y ago

I'm beginning to think that Substack the new Medium, and this cannot and will never be solved. 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.

red2awn 2y ago

Stopped reading after this > 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.

djtango 2y ago
1 payment per second. 1 payment per uber ride. 10 dollars per ride. 864k per day. 365M per year. It's not a small system and could be some mixture of one market at Uber or some %age of rides (eg one payment provider) (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
- deserted 2y ago
  The author works at Kiwi.com, and says there are '70,000 times a day a customer clicks the Pay button on our platform' which is a little under 1 QPS. 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.

tivert 2y ago

> Extremely fluffy piece. 20% in and not one valuable piece of information 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