I don't start with technologies.
I start with friction.
Most of my projects begin the same way. I become obsessed with a question I can't stop thinking about.
- Why is finding a public restroom so difficult for someone who needs one?
- Why is important information trapped inside documents that no one can navigate?
- Why do websites optimize for bots instead of people?
- Why do students disappear from educational systems without anyone noticing?
Those questions eventually became projects. Once I find where a system is harder than it needs to be, I tend to stay there until I understand it well enough to try to fix it.
I work best in small teams where the problem matters more than the process, and where the person using the software is someone most products weren't designed for.
"Most systems make sense once you find where the friction lives."
- AI adoption inside organizations
- Information accessibility and civic technology
- Operational workflows and automation
- Human-centered systems design
Python · TypeScript · SQL · React Native · Claude API
Tools change. The problems worth solving usually don't.
What I'm interested in
Information Access
I'm interested in the places where information exists but remains difficult to find, understand, or use. Whether it's public infrastructure, policy documents, or organizational knowledge, I'm drawn to making important information more accessible.
Operational Friction
Most of my projects begin with a workflow that feels harder than it should be. I enjoy finding unnecessary complexity and designing systems that reduce it.
People & Systems
The most interesting problems live at the boundary between people and complicated systems. Good software helps the interaction feel simpler without hiding the complexity underneath.
Writing
Building helps me understand systems. Writing helps me understand what I learned. Most of my essays are attempts to make sense of projects after they're finished.