About

I am a solution architect and software engineer. I spend most of my time on systems that have to keep working once they get big, and on the practical question of how to build them alongside agents.

Why this site exists

Writing is how I find out whether I actually understand something. Half of what is here is unfinished on purpose — the unfinished parts are the honest ones.

How it is organised

Four formats, sorted by how finished the thinking is rather than by subject:

• Essays are arguments I am ready to defend.
• Notes are thinking out loud, often wrong.
• Playbooks are decisions I have made more than once.
• Signals are links worth exactly two sentences.

Topics cut across all four. A subject can show up as a signal today and an essay a year later, which is roughly how understanding works.

Elsewhere

Code on GitHub. Offline: Pokémon, co-op games, long strategy games, and two cats with strong opinions about my keyboard.