Architecture · Reliability · Legibility
Systems that explain themselves
I’m drawn to software whose boundaries, failure modes, and tradeoffs remain visible to the people who build and use it.
Legibility is a feature
The best systems are not necessarily simple, but they make their complexity accountable. You can trace what happened, understand which boundary failed, and change one part without discovering three hidden contracts.
I enjoy architecture work because it turns those qualities into concrete decisions: dependency direction, state ownership, interfaces, observability, and the failure modes a design chooses to make cheap.
This is also why I value small tools. A narrow product surface creates room to make the underlying system unusually clear.