Been trying to use https://conductor.build/ to run some Claude Code agents in the background while I write some documents. Seems pretty great so far and has a really nice UI/UX for creating PRs.
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.
I do the research I do the plan I do the implementation I throw the docs out and the next time I need research I just do it from scratch because tokens are cheap and my time is expensive
the ballerina and the kind of performer, that's the wrong reference class. Right now we have a lot of jobs where you have different tasks. So this is the task-based model jobs where you have like a lot of different tasks. So like a doctor, what is their job? They're filling out insurance documents. They're you know, going and like calling different pharmaceutical companies. And one of their tasks is to actually see the patient and talk to them, but that's like actually not the main part part of the job.
The second is that most of the work that you do is actually going to happen on your computer in an environment like Codex or Cloud Co-work that becomes the sort of operating system for it becomes the sort of operating system for how how you do all of your work, whether that's your email, the documents you create, like all that kind of stuff.
did you know that according to the legal documents you yourself signed, your company's literal charter that you have right now, and this is not some hypothetical future thing, you've already put in motion, a rule that says you have a fiduciary duty to say yes in this situation.
According to Harvard Law School, among venturebacked companies that have the standard best practices set up that you got from your lawyer, okay, only 20% of founders are still the CEO 3 years after going public.
It used to be that you have documentation for other people who are going to use your library, but like you shouldn't do that anymore. Like you should have instead of HTML documents for humans, you have markdown documents for agents.
Because of how source survival works, or indeed, how architectural survival works, we are often encouraged to think of the past as a place populated entirely by the wealthy elite.
So the Navy hired the shoe runners unit from the SS, paid them money, and then gave them drugs, different kinds of drug combinations, methamphetamine combined with cocaine and chewing gum and all kinds of things. So this is a big thing, you know. And there are documents to it.
Say goodbye to cycles of mock and doc feedback, and say hello to code-first prototypes with constant iteration (on prompts, models, etc) to answer three key questions.
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.