264 karma · joined February 24, 2019
The whole business of Stripe is based on that: it's so hard for developers to do, and so many regulations, that they would rather pay an another company to do so.
Crypto can be sent just using a contract.transfer() call
Let's say a part of the subscription is used to pay for it.
So if: cost monetized API < cost configuring scraper for your website OR feature provided by premium api > data got by scraping, then some people/business will likely pay
Having an almost a plug and play solution who does CDN + DDoS Protection + WAF/Rate Limiter + Bot Protection, for a few bucks, is very useful for startups and SMEs.
And compared to cloud different offerings, their quick setup and lower cost is hard to beat.
I personally have a stammer. While mine is less severe, and I doesn't need directly it, I know several people that would quite be glad of the benefits that it could bring to them. (Example: pass online interviews).
I agree however of the privacy concerns. We could limit it in a first time to medical devices for example, or have some privacy laws in place.
In the same way than Amazon spin-up AWS, they are quite leveraging their tech experience.
There is no marketing like Uber did sometimes of like: "personal service, free water bottle", and it's still killing it.
Of course, I personally always enjoy a chat with the driver, but many people I know prefer actually not talking.
But what about a company which is more in B2B, and where procurement will be more rationalized (e.g RFP, which is often regulated)?
One thing as well: this is moat from an organization point of view, but unfortunately not for the individual: soft skills are often easier to get than hard skills, and there is so already a competition on the job market for the client-facing roles, even before AI arrival: like Sales / Business Developers / Account Managers (or more internal roles to try to build something that the client would need, like Product Managers)
Exemple:
``` QUERY /search HTTP/1.1 Content-Type: application/json
{ "filters": { "region": "asia", "status": "active" }, "sort": "created_at", "limit": 500 } ```
can answer
``` HTTP/1.1 303 See Other Location: /queries/results/f3a9c1d7 ```
And then you can access later `/queries/results/f3a9c1d7` using a pure GET call, and cache this instead
In the industry, almost everyone here is doing the exact same thing, outsourcing more and more of their thinking to LLM: so even if students learned how to manually write code, they will probably loose it later on (happening to us already, mostly can be seen when people are working on new solutions/frameworks... they now have the same issue than students).
Capital expenditures are easy to calculate, and it's easy to help raising money. As the current economical system is based on debts, it works quite well: if a company knows that productivity output will raise by 15% over the next year if they spend X dollars, it's easy to get investments (investments firms themselves are relying heavily on private credits, which more and more is coming from bank too). With a system based on debts, they care less about the amount spent, than the yield generated.
With investing in people, it's harder to predict.
Industry does it by buying machines, now knowledge-based companies might do it with GPUs or tokens.
Both are at the same levels at +5 years after high-school, but they leads to different career paths.
So everyone feels the needs to talk about it, to either get rid of this anxiety by ranting or trying to prove that it would be an opportunity, or a non-event depending on the point of view, etc