The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
AIs don’t just repeat the same sentence patterns but also the same themes (memory is a favorite), names (Elara Voss, Marcus Chen), and underlying ideas.
Now you can have a quake style console in your operating system. Except with an infinitely patient agent to help you customize it instead of esoteric variable names and slash commands like in the 90s
Smalltalk Best Practice Patterns. True, Kent Beck is better known for his later work, which is excellent too. But Smalltalk Best Practice Patterns is particularly strong on coding style. I learned a lot by just reading the code examples. Small tweaks to names and abstractions add up. No one captures that better than Kent.
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.
I think this is kind of leads to another way that Rust really helps with reliability, which is that if you're refactoring, I think Rust is really good at telling you all the places you need to update. I've done this sometimes where I would refactor something. I change the code. I change the return type or whatever it is, and then I just fix the compiler errors and until the compiler stops shouting. And then once I've done that, I've updated every place I need to update.
I- i- like, we are in a stage where I'm not building the code base to be perfect for me, but I wanna build a code base that is very easy for an agent to navigate.
But Amap is great! Especially since it can be used in English and I think it transliterates your searches to Chinese and the Chinese place names back to English
And so I would say, yes, we are just giving proxy names to things we don’t understand, but to dismiss that as some kind of, “Oh, they just don’t know…” It is actually quite the opposite.
But what we actually found was that none of those are actually hard. The whole idea of hard steps, that there are hard steps, is actually suspect. What's amazing about this model is it shows how important it is to actually work with people who are in the field.
Archeology, in this regard, is the worst enemy of this. So we put these names on cultures, we talk about how they evolve from one to another, we draw these lines where there aren’t any.
For the most part, it’s like these names are just utterly arbitrary, so you have no thing to latch on to. It’s not really a thing that our brain does very well to learn meaningless, arbitrary stuff. So what you need to do is build connections somehow, visualize a connection, and sometimes it’s obvious or sometimes it’s not.
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.