A short
field note.
I'm a software engineer in Northern California. I work at Nike on backend and platform systems for privacy and consent.
Before Nike, I built consumer web and AWS-backed mobile services for Hestan Smart Cooking. Before software, I was an auditor. That accounting background still shows up in how I build systems: controls, evidence, clear ownership, and a useful paper trail.
The work I like is practical systems work: a data model people can explain, a service boundary that is not mysterious, a deploy path with a way back, alerts that point somewhere useful, and notes that save the next person from guessing. Lately I have been using AI-assisted tools in that same mode: useful when they make work easier to inspect, not when they make it harder to tell what happened.
- Reading
- A Philosophy of Software Design
- Listening
- Floating Points — Promises
- Building
- small local tools for checking systems and keeping notes
- Carrying
- Olympus Pen-F, mostly for the weight