Launch notes, experiments, and standalone writing.

A judgment support tool has one job: make your current intention the easiest thing to act on. Here's what that means — and what it rules out.

Platforms aren't stealing your attention. They're consuming it structurally — and willpower isn't a defense against structural problems.

As AI gets better at execution, the bottleneck shifts entirely to judgment. And we're building almost nothing to protect it.

We have tools for doing things and tools for blocking things. The third category — judgment support — barely exists. Here's what it would actually look like.

The problem isn't your system. It's what your system does when reality hits it — and why that turns judgment failures into personal ones.

Every productivity tool shares a hidden assumption: you already know what to do. That assumption might be what's making your perfectly organized task list feel hollow.

A founder note on building AI-native organizations and systems.

This is the fifth and final article in our series, "From Rural Towns to the future of Humanity: A Thought Experiment on an Economic Model." Thank you for following along.

This is the fourth article in our series, "From Rural Towns to the Future of Humanity: A Thought Experiment on an Economic Model." Please stay tuned for subsequent articles.

This is the third article in our series, "From Rural Towns to the Future of Humanity: A Thought Experiment on an Economic Model." Please stay tuned for subsequent articles.

This is the second article in our series, "From Rural Towns to the Future of Humanity: A Thought Experiment on an Economic Model." Please stay tuned for subsequent articles.

This is the first article in our series, "From Rural Towns to the Future of Humanity: A Thought Experiment on an Economic Model." Please stay tuned for subsequent articles.

The origin of this article was a continuously deepening dialogue between myself and an AI. It began with a technical question about the future business models of software, yet l...

How doubling your codebase creates completely different engineering challenges - and why most teams aren't prepared for the transitions.
The 13-chapter sequence collected in one place.

Understanding AI hinges on understanding its statelessness. Your codebase should shed all procedural and historical baggage so that any reader—every AI session—needs zero historical context to operate...

You must spend a lot of time—more than 50%—writing testing code.

Today's AI programming is programming in uncertainty, in chaos, in confusion.