438 karma · joined June 25, 2018
For who? Will it ever be read? I’m bias on good documentation and I think AI is better at publishing documents for machines, for now.
Since Stripe operates by working with a BIN (banks that sponsor them within each country) generally like all payment providers. While the decline rates for new customers are not public, they are very high, especially for industries that aren’t allowed like Adult Content, Weapons, and Gambling [1]. Also revocation of existing accounts can happen often if KYC systems flag anything, like Stripe Identity, Connect, and Radar.
Also running payment processor per country would not be an easy feat or probably feasible.
It’s a clear pattern in service delivery for software for a while now. Hell for many goods and services in general, like Uber rides themselves.
Start cheap, get some vendor lock in, service provider reduces discounts, consumer notices and then reacts to the price by reducing consumption.
The topic was about sentiment, not usage. And the Pew Article has broad sample sizes ranging from 5,000 to 28,000.
Then you have the many companies in the UK, US, Canada, EU that have compliance and regulatory laws that require them to exist in some capacity in house. Though that is changing with MDR services, but someone still has to interface with the MDR.
[1]: https://www.elastic.co/pdf/sans-soc-survey-2025.pdf [2]: https://github.com/jacobdjwilson/awesome-annual-security-rep...
> It's is a complex and hard question, but the principles we apply to it have been around for a long time and are consistent with the site guidelines. If they weren't, we'd change the latter. > > I've explained all of this many times. If you, or anyone, would like to know how we approach the question, you could start here: > > https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... [1]
https://www.sciencedirect.com/science/article/pii/S105113772...
Why should we assume this for every type of business.
> The thing that makes these providers worth it, is that it lets the business focus on their core competencies and just add-on as they scale without worrying about complexity.
Since when? Mastering the complexity and implementation of infrastructure from US cloud providers is a skill that takes time in itself. Personally I don’t see how Scaleway does not provide the same for example.
At some point we have to question are we choosing AWS, GCP, or Azure out of brand name, convenience, and marketability. Our if they actually enable faster business execution, higher availability, security, and regional compliance that alternatives don’t…
I’ve definitely had roles where I sadly realized I’m automating the QA person next to me well before LLMs were mainstream.
In my experience I think, you would automate enough of a mid manager role that upper management doesn’t care for, and whatever left over responsibilities that couldn’t be automated is split between a high level IC and the next above. Then the bureaucracy sells is as a success.
I don’t know if you are intentionally being vague and existential here. However, context matters, and the predictive power is zero sounds unreasonable in the face of history.
I think humans learning that diseases were affecting us and thus leading to solutions like antibiotics and vaccines. It was not guaranteed, but I’m skeptical of the predictive power being zero.
[1]: https://www.google.com/travel/hotels/Houston%2C%20TX/entity/...