Complexity belongs in the system.
The interface should carry enough structure to be powerful without making users absorb the implementation model.
Profile / 01Engineer by trade.
Engineer by trade.
Builder by nature.
I'm a frontend engineer architect with 15+ years of experience building web products, leading teams, and working across the line between design and engineering.
Details communicate quality.
Interaction timing, language, spacing, and edge cases shape trust long before anyone inspects the architecture.
Strong opinions need evidence.
Direct communication is useful when it stays attached to user needs, technical constraints, and actual outcomes.
History / 02
From view source to product systems.
I started by inspecting website source code, then co-founded a design agency right out of college. Building products for clients and ourselves eventually led to the company being acquired.
Working across backend and frontend systems taught me that my best work happens where product behavior, interface design, and engineering constraints all meet. That has led to larger teams, leadership roles, and plenty of hands-on building.
More recently, I've focused on AI products and research tools: systems with powerful behavior that need unusually clear interfaces to earn trust.
Off-screen / 0301 / Golf 02 / Fishing 
Golf and fishing.
Outside of work, I spend as much time as I can playing golf and fishing. I love the focus, patience, and constant room to improve in both. When I'm not on a course or near the water, I'm usually outside with my wife and our two Australian Shepherds.
Always working on the next round.
I enjoy the technical details, the competition, and the fact that there is always another part of the game to sharpen.
Time near the water.
Fishing gives me a reason to slow down, pay attention, and spend a long stretch of the day outside.