About
Physics first, then software.
The short version
I studied physics at UBC, which mostly taught me how to sit with a problem I do not understand yet. The programming started as a way to get through problem sets, then took over.
Since 2024 I have been a clinical informatics analyst at Interior Health Authority, working on the scheduling module that clinics across the region use to book patients. Healthcare software is unglamorous and deeply constrained, and it is the best training I have had. Nothing sharpens your sense of edge cases like a system where an edge case is a person who does not get seen.
Before that I built and shipped products: an event discovery platform with a live map and ticketing, a white label ticketing site, a social analytics tool for a small team, and API work in C# during an internship in Jakarta. The through line is that I like owning something end to end, from the data model out to whether it feels good on a phone.
Outside of work I sing. I was in an acapella club through university and it is still the fastest way I know to stop thinking about software for an hour.
How I like to build
- Ship the smallest honest version, then make it good under real use.
- Static and server rendered by default. Client JavaScript needs to earn its place.
- Accessibility and keyboard behaviour are part of the feature, not a pass at the end.
- Test the paths that would actually embarrass you if they broke.