I came to design through code,
and I never really left either one.

I studied Human-Centered Computing at RIT, which sits deliberately between psychology and computer science. That combination is still how I work. I want to know why someone hesitates before a button, and I also want to know what it will take to build the thing that removes the hesitation.

Most of my work has been in systems where being wrong is expensive. Right now that is a pharmacy platform serving five long-term care locations, where a mis-clicked field can misroute a prescription. Before that it was research for enterprise teams at Fortune 500 companies, and before that UI development in Angular for a collaborative document platform whose patent application names me as an inventor.

The part I care most about is the unglamorous part: sitting with the people who use the software, learning their vocabulary, and finding out which of their workarounds are actually the design telling on itself. Domain knowledge is not background reading for this kind of work. It is the work.

I also write the front end. React and TypeScript on the web, SwiftUI on iOS. It means my prototypes run in the real stack, my handoffs are short, and I can argue with an engineer in their own terms, which usually turns out to be the fastest way to a better answer.