Chokepoint risk does more than spike the spot price for a season. It re-prices geography permanently: it redirects the next decade of pipeline and terminal investment and hands a windfall to whoever sits on the alternative route.
This is pretty neat: ChatGPT Work and GPT-6 Astra (I used "Max") can take an address and produce a 5K/10K circular running route starting from that address, using OSM data
This is pretty neat: ChatGPT Work and GPT-6 Astra (I used "Max") can take an address and produce a 5K/10K circular running route starting from that address, using OSM data
Don't try to anticipate anything. You will literally go crazy. Because even the smartest brains in the business cannot anticipate what two model hops from here is going to look like. It's an absolute waste of time, and you will develop an AI psychosis trying to deduce what two years from now is gonna look like. Focus on right now, and right now is the most incredible time to be into computers.
With thousands of developed in a mono repo, it just does happen that one directory is missing one of the two files and this means that a subset of devs work with lobotomy. We fix this with automation but it’s a stupid complexity tax that shouldn’t have to be paid.
if you do for some reason generalize maladaptively to thinking this didn't work and I tried this, this didn't work, and I tried this and I'm really bad at this. That can lead not only to loss of motivation, but what we might call clinical depression.
Since I mostly work on Laravel projects or packages, I usually enable the Laravel Idea plugin. It's a paid plugin, but it's definitely worth the money since it can provide stuff like auto-completions for route names, request fields and more.
Also, not only is it far cheaper to send things by sea, it is far more secure. If you're going to run the Belt Road thing, uh or it's it's the belt part of it, the land part, um you've got to control the whole thing end to end. You're going through some of the most unstable places there are.
My opinion is that the least mature area is front end. There have been some attempts to compile Rust to Web Assembly and then run it on the web as a front end as a replacement for TypeScript. But if I was writing a web server, I would totally use Rust for the back end and TypeScript for the front end. I would not really go the web assembly route.
First, because it signals how much collateral damage the A.I. companies will tolerate en route to A.G.I. And second, because the production of a social underclass is a policy choice.
Yeah, we we could do all of those things. Um it's just not better. And we simulate it all. they're in our simulator provably worse and so we wouldn't do it.
building a third-party client to read and route messages is a gray area in their terms of service, and perhaps only partially supported in their API surfaces.
basically transplant patients today surprisingly frequently miss organs that are on route to them because there's a timing problem. Um, so like you know, organs expire um very quickly after they become available from a donor.
like what we see is that over 75% of our new users, they classify themselves as like, I'm completely new to chess or I'm a beginner. And unfortunately, if you're new to chess and you're a beginner, you're not going to have that fun of a time playing live games. We see this in the data. It's like less than a third of those users actually win their first game. And when you lose a game, user retention is 10% worse than when you win a game.
it's something like this that the brain is extremely parallel. uh it kind of has to be just out of just because of the biohysics. U but like it's even more parallel than your GPU.
If a new monetary network with its own unit (i.e. not pegged to an existing currency as a credit rail on top of it, but rather a fully parallel system to central banks) is going to bootstrap from zero to massive, it requires upward volatility.
Many of them try to pretend the measurement problem isn't there. Go to enormous lengths like the many-worlds interpretation, literally inventing an infinite number of unobservable parallel universes to avoid the thing that quantum mechanics is telling them, which is that measurements matter.
So Tesla hasn’t found a different, better way to bring driverless technology to market. Waymo is just so far ahead that it’s dealing with challenges Tesla hasn’t started thinking about.
What’s ironic about all these AI safety people is they’re going to build the exact thing they fear. We need to have one model that we control and align. This is the only way you end up paper clipped. There’s no way you end up paper clipped if everybody has an AI.
This book takes a different route and that's why I found it hugely influential and interesting when I read it back in 2000. It was co- authored by Edelman and Giulio Tononi.
The fast route — venture capital funded — is going to impose constraints on your business that will ultimately make it difficult to remain true to your open-source mission.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.