This is the first post on my portfolio blog. I'm planning to write about projects I'm shipping, engineering problems I run into, and things I learn along the way.
Why a blog?
Because writing it down forces clarity. A solution that's clear in my head is often muddled the moment I try to put it on the page — and the muddled bits are usually where I haven't actually thought hard enough.
What to expect
- Project deep-dives — what I built, the tradeoffs, what I'd do differently.
- Debugging stories — the kind of bugs that take a day to find and a one-line fix.
- Notes on tools I'm using day-to-day.
If you want to reach me, the contact form on this site sends straight to my inbox.