Architecture is the set of decisions that outlast implementation. I approach it as explicit tradeoffs: consistency vs. availability, latency vs. throughput, dependency count vs. speed of delivery.

Recurring themes: minimal surface area, clear boundaries, performance as a requirement from day one, and the conviction that the best dependency is the one you don't add.

For deep dives see Work and Essays.