Store what happened, not what is: one append-only journal, everything else derived — and whole categories of bugs become impossible by construction. With goats.

The C++ overload resolution spec is a sort predicate written as legal prose. It could be six lines of Haskell. It's still prose — and the reasons are institutional, not technical.

Agents don't accelerate the observability loop. They close it — and a closed loop has no observer.

A shitpost and a Zen koan occupy different cells in the same table.

Base units, work, and what your architecture is actually optimizing for.

A dialogue on virtue, ego, and what kind of god would look down its nose at someone who lived with integrity.

Git history is the empirical complection field. Here's how to read it.

Monorepos, microservices, DRY, Conway's Law — each a strategy for managing the complection field.

Coupling isn't a number. It's a field — a function of what you're trying to do.

What if layoff risk had a market price — and workers could see it moving before the axe fell?

A twenty-year path from the current system to LVT — without crashing land prices or drowning homeowners.

Legitimacy, force, commissions, and why the system doesn't need growth to survive.

What if the franchise required something from you first?

Henry George's cleanest insight, extended to everything scarce and unearned.

A Socratic dialogue on why we judge every other system by its implementations — and should do the same here.

We engineer code, infrastructure, deploys. The context we work inside? Left to chance.

Your brain has been running a language model for millennia. The external one is the copy.

Political centrism is Celsius zero — calibrated to convenience, not structure. What if we measured politics the way Kelvin measures temperature?

Complexity breeds fragility, fragility breeds distrust, and none of it self-corrects when the feedback is hidden.

Industrial farms optimize for labour, not land. That's the opposite of what we need.

I coined a word, Googled it, and found out the idea already has a life of its own. The pattern keeps showing up.

Pointers, references, and value semantics are three different things. The confusion is persistent and the distinctions matter.

The conventional wisdom is that concurrency is hard for humans. I think it's exactly backwards — sequential thought is the unnatural one.

Language isn't distinguished from mere protocol by complexity. It's distinguished by the ability to describe itself.

A 2006 thought experiment about what OS X could become if Apple built it on Plan 9's exportable filesystems. Much of it actually happened.