I build software that stays simple as it grows.

The best systems I've worked on were never the cleverest. They were the ones that were easy to reason about at 3 a.m., easy for the next person to change, and quiet when nothing was wrong.

That's the work I care about:

• Clarity over cleverness. Code is read far more than it's written. The right abstraction is the one that disappears.
• Design for change. Requirements move. Good architecture absorbs that motion instead of fighting it.
• Earn complexity. Every layer should pay for itself. When it stops, it goes.
• Build people, not just systems. The deepest leverage is a team that makes good decisions without you in the room.

Most of my work has been in backend and distributed systems, mostly with Python and the cloud. But the tools are the easy part. What carries over from one project to the next is judgment: knowing what to build, what to leave out, and when something is good enough.

In the age of AI - You can outsource work, but not your understanding.