Just built my first Omarchy plugin! This also happens to be the first piece of software I've ever made solo entirely with AI. Back-and-forth over English and nothing else. So two firsts for me. Super fun experience. Here's a quick little tour. Hope you dig it.
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.
Omarchy is not going to adopt a formal Code of Conduct because those turned out to be struggle-session processes in the last turning. But we are going to play nice. We're going to be courteous, professional, and composed in our direct interactions with users, competitors, and even haters. Because that's what's going to pave the path to the win.
Maybe Nix is like Rust: Amazing if you don't have to look at the code! I'm open to the idea that Omarchy Cinque could switch packaging system if I never have to look at nixlang, there are no ergonomic regressions, and we have full repo sovereignty.
The revelation I've had working on Omarchy the last three months is that to get that magical 10X, 100X, in a few rare cases, 1000X productivity boost, you have to interact with the agents directly, and you cannot intermediate that bandwidth with another human because it's simply too slow.
I don't require anyone to be as excited about AI or agents as I am. It's completely fine. But we also need someone in this camp in this Linux camp who are really excited about AI, who really leaning in with agents.
This is a computer system made for pros, and I mean that in the sense of professional computer lovers. People who are willing to invest time and energy into learning how their system works, and reap the benefits that come from that investment.
AI checkers are essentially a cat-and-mouse game. AI checkers may learn to detect a certain pattern that is indicative of AI-generated content. Then, the next LLM may incidentally or deliberately not exhibit that pattern and avoid detection. The AI checker then has to be updated to detect said LLM, and so forth.
Thinking Forth by Leo Brodie. I used to have this habit where I learned various programming languages. To challenge my perspective, I chose languages from families and paradigms that were fundamentally different from what I already knew. Occasionally, I stumbled upon greatness. Thinking Forth presents programming as a creative process, and it delivers those lessons in an entertaining and pedagogical way. The book is particularly strong on software analysis and design, but it's the execution and technical writing that brought the book to my top five. This is the book for anyone writing about software — Leo's way is the way to do it.
And just human organizations are complicated and it's very hard to have um to manage to aggressively prosecute 100 different priorities and to deal with all the issues and interference that arises among them and so forth. And so, you know, Google has done incredibly well in a bunch of specific places, but it's not like Google has done all the things even if in some kind of basic material sense, uh Google maybe, you know, had that ability.
You know, I think a lot of parents think that dropping out is very risky and impune your reputation for the rest of your life and so forth. And as far as I can tell, nobody has ever cared.
But yeah, there's been a back and forth about whether dinosaurs were already on their way out or were they a bit limited by the very end of the Cretaceous. I think the more recent analyses have shown that's probably not the case, because in other words, they were basically doing fine right up to the extinction event. And so yeah, if the asteroid hadn't hit, there's no reason to think that they were on some kind of terminal decline.
But this great system that united, it's called the Yam or Ortogh, that had united everything, people could move back and forth quickly that it could also take the plague out of Southern China into all parts of the world. And I do think that's what happened. And the plague destroyed the Mongol system.
An unconventional guide to the craft of indie consulting and life in the gig economy, mixing philosophy, pattern language, and very practical guidance for building a client-based solo career.
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.