About

I work on engineering systems that improve leverage: architecture boundaries, AI-assisted development, developer infrastructure, and the operational mechanics that determine whether software teams get faster or slower over time.

Most of the writing here focuses on one question:

How do you increase execution speed without increasing entropy?

That usually turns into discussions about:

• architecture and cost of change
• development infrastructure
• review economics
• AI execution workflows
• ownership boundaries
• operational simplicity
• developer experience under real constraints

I prefer systems that are:

• understandable
• composable
• operationally boring
• easy to recover
• difficult to misuse accidentally

This site intentionally stays simple:

plain HTML
minimal JavaScript
durable links
small surface area

The goal is clarity, not platform theater.