About me
I'm a software engineer who likes problems with a sharp edge to them — the ones where the naive solution works fine until it very suddenly doesn't.
📷 assets/img/portrait.jpg
I wrote my first real program because I was annoyed. A spreadsheet I maintained by hand kept drifting out of sync, and it turned out a hundred lines of script could make the problem disappear forever. That trade — a bounded amount of thinking in exchange for an unbounded amount of not-doing-the-boring-thing — is still the thing I find most satisfying about this work.
Since then I've worked across the stack: backend services that need to stay up, frontends that need to feel instant, and the unglamorous glue in between. I've learned that most engineering wins come from deleting a step rather than optimizing it.
The interesting requirements never show up in the happy path. I design from the failure case backwards.
I'd rather ship five changes I can roll back than one I have to defend.
Opinions about performance are cheap. A flame graph settles it in a minute.
If I can't explain the design in a page, I don't understand it yet.
The things I reach for without thinking, and the things I'm deliberately getting better at.
Education
Your University
Distributed Systems · Compilers · Databases · Algorithms · HCI
"Simplicity is prerequisite for reliability."
The résumé has the dates and the bullet points. The Life page has everything else.