Software engineer · curious generalist

I build reliable systems and write down what I learn.

This is my small corner of the internet: part résumé, part engineering notebook, and part record of the ideas worth revisiting.

Distributed systemsDeveloper experienceTechnical leadershipUseful writingThoughtful products

Engineering is mostly about making good decisions with incomplete information.

I’m a software engineer who enjoys turning ambiguous problems into systems that are understandable, dependable, and pleasant to use. My work sits at the intersection of technical depth, product judgment, and clear communication.

I care about the details that compound: sensible interfaces, boring operations, useful documentation, and teams where people can do their best work. Away from the keyboard, I’m usually reading, taking notes, or following a question further than necessary.

  • Make it clearClarity scales better than cleverness.
  • Own the outcomeThe work ends when the problem does.
  • Leave a trailWrite so the next person starts ahead.

A second life for a meaningful address

Why this domain?

This domain belonged to the first company I worked for. It represents an important chapter: the people who took a chance on me, the problems that shaped how I think, and the place where a career began.

After the company was acquired, the domain was eventually released. I bought it—not to recreate what was here, but to give the address a new purpose. What once introduced a company now holds one person’s work, lessons, and evolving point of view.

Read the full story

Notes from the workbench.

All writing

Designing systems for the person on call

Reliability decisions look different when you picture the human receiving the alert.

Draft

What I mean when I say “simple”

Less code is not always less complexity. A practical vocabulary for better tradeoffs.

Draft

Have an interesting problem or a thoughtful disagreement?

Those are usually the best reasons to talk. Find me on LinkedIn or GitHub.