All those things you can easily measure in isolation, and you can also optimize for them quite locally. But these local optimizations do not produce global optimums, and the fewer of us are looking at the output, the less it matters.
New: emulate a GitHub App in a few lines of TypeScript Generated App keys, installation auth and stateful repository APIs Develop locally, test in CI or give sandboxed agents their own isolated GitHub environment
I even switched to local CI, you know, like DHH inspired where I don't care so much more about the CI on GitHub. We still have it. It's still, it still has a place, but I just run tests locally and if they work locally, I push to main.
If you do too much exploration, you can have your team feel a little bit too scattershot, just trying a 100 different random ideas. What's the through line? What's the strategy? How do you pattern match, you know, successes across them? And if you do too much in exploitation, which is often the MMO of growth teams, it can lead to this like saturation and stagnation where you're just locally maximizing a thing.
But the one thing that they valued were all the artisans, everybody who had a skill. And that skill could be making a pot. It could be hammering out a metal plate. It can be weaving carpets, it can be translating or just reading and writing. Every person with a skill was spared.
I’m going back to the vacuum. The empty space, the beautiful event horizon I’ll give up locality, meaning that I will allow things to be connected non-locally by a wormhole.
This allows me to run models locally on my MacBook Pro M1 Max. With the 64GB of RAM it has, it’s a pretty potent machine for basic inference despite it being three years old.
Yield-boosting measures, however, always need to be thoughtfully paired with other measures to ensure that outcomes—environmental as well as social—are acceptable at the local level.
So generally, I think we obviously want to prioritize civilizational risks over things that are painful and tragic on a local level, but not civilizational.
The tyranny of the wagon equation is thus inescapable: an army that plans to be in the field for more than just a few days cannot bring all of the food it needs with it; it must find most of its food locally.
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.