They were only touched on (and just barely) in my CS education, so don’t feel too left out. Spend an evening or two on the Wiki for Probabilistic data structures[0]. With a CS education you should have the baseline knowledge to find them really fascinating. Enjoy!
Oh, and
I don’t find myself actually implementing any of these very often or knowing that they are in use. I occasionally use things like APPROX_COUNT_DISTINCT in Snowflake[1], which is a HyperLogLog (linked in the Wiki).
I've really been enjoying Complex Systems with Patrick McKenzie (patio11) of HN fame. Additionally: Odd Lots, Money Stuff, Chat with Traders (hit or miss, some guests are not great).
Audiobook publishers require/request this when you sell subsidiary rights. We’ve been able to push back citing accessibility concerns. I find it really annoying when not available for my own reading.
For Shopify in particular, they have a headless front-end services called Hydrogen[0] (with optional hosting called Oxygen). It's basically an opinionated wrapper around the storefront[1] and customer account[2] APIs, which allows interacting with the store from the front-end. It allows you to host Shopify on your own domain under your own control and gives a bit more customization than is available via hosted Shopify. It's what I run for the Creature Publishing site[3] and allows some extra customization for wholesale accounts, etc, without the exceptionally expensive enterprise (Shopify Plus) plan. To be completely honest, sometimes I question the decision over a simple hosted shop subdomain. Some light SSR/API calls are necessary for our setup, which is hosted on Cloudflare Pages/Workers.
It does, however, make providing housing more profitable, which, on the margins, will drive more landlords and home builders into the market, decreasing long term costs (relative to a straight 100% increase relative to the basic income). So you might send everyone $100 per month and costs go up $100 per month, until supply chains shift towards supplying lower income humans with more goods and services than they used to get, at which point costs will decrease (from the $100 increase).
With enough forewarning, suppliers could anticipate the increased demand and prepare for it.
The trouble is, you have to place the outbound call to those contacts to trust them. People could spoof an incoming call from numbers in your contacts and it will look as legitimate to you as a receiver as if the real number was calling you. With voice spoofing, it's now possible to call someone as [grandchild] with [grandchild]'s voice with a pretty horrible story about what's going to happen if some Bitcoin or Google Play gift cards are not purchased and handed over immediately.
IMO the game is to get the highest credit score while spending the least on credit. That way if you e.g. need to acquire housing, a reliable vehicle, business loans, even employment or insurance, you will be able to and can get a good deal. Sure, paying nothing saves you money, but it also costs you the opportunity cost between what you could earn/save by utilizing credit vs waiting months to years to save up and pay cash.
I’m not sure. I’m sophisticated enough to use BNPL and set aside the funds in a HYSA, but I never have as you miss out on: credit card rewards, credit card purchase protection, credit card extended warranties, credit card chargeback infrastructure. Additionally, I’ve seen BNPL offers where the first payment is in 2 weeks compared to 30-50 days for credit cards depending on when your statement closes and how soon you have to pay, so the extra interest is less than you might think. It could make sense for very large purchases, but then, that’s also where credit card features can really come in handy.
Like you, I’m far too risk averse to not fact check everything an LLM outputs, but I’ve also fixed bugs that have been present for 5+ years. Maybe at a certain point you can just wait for the next generation of model to fix the bugs. And wait for the generation after that to fix the newly introduced and/or more subtle bugs.
This is interesting to me—are you an app developer that does this pattern for that reason? I definitely figured it was exclusively because they can request repeatedly for the fake prompt, and only “use” their prompt when the user is inclined to accept. There are times where I’ll accept the first prompt and reject the second prompt when apps are spammy about it.
Another case of Hyrum's Law, where the entire functionality of the S3 SDK and any competing service provider borrowing from it becomes Amazon's problem to fix at their own cost. Maybe it's time for a non-Amazon but S3 API compatible library to emerge among the other cloud storage providers offering S3 compatible APIs. OpenDAL looks interesting. Also another reminder to run thorough integration tests before updating your dependencies.
I think so, but not a bad marketing gimmick. It gives a pretty easy way for the general public to interact with ChatGPT on a trial basis without signing up or paying for it using a somewhat hard to acquire identifier (phone number). I'm curious if they're doing anything to avoid abuse from spoofed numbers.
I think we should start doing more taxes combined with subsidies. Give everyone a $1/t carbon tax. Give everyone a ~$1/t farming subsidy based on current carbon production. Nobody loses, but everyone is incentivized to decrease carbon production and the faster ones profit more. Phase out the subsidy over X years if you like.
Otherwise, you’re right. We’re upsetting the balance of a very complex, very important system and causing a regressive tax in the form of price increases.
[ my public key: https://keybase.io/benmanns; my proof: https://keybase.io/benmanns/sigs/JFJN7xRYb-_qIdTe8VkPTshHZSbPBUzdgVlxWuzcDe8 ]