Engineer · Photographer · Writer

I build calm, considered software — and photograph the quiet moments in between.

I'm a systems engineer who cares about craft: legible code, honest interfaces, and tools that get out of the way. Off the clock, I'm usually somewhere with a camera.


About

For the last decade I’ve worked on the unglamorous middle of the stack — the queues, pipelines and platforms that quietly hold products together. I like problems that reward patience, and systems that are still understandable a year later.

This site is my home base: a few projects worth showing, notes I write to think more clearly, and an ever-growing archive of photographs.

More about me →

Certifications

All credentials →

AWS Certified Solutions Architect – Professional

Amazon Web Services
2025

Certified Kubernetes Administrator (CKA)

Cloud Native Computing Foundation
2024

HashiCorp Terraform Associate

HashiCorp
2023

Google Professional Cloud Architect

Google Cloud
2022

Selected projects

All projects →
Relay — a self-healing data pipeline
2025 Lead engineer

Relay — a self-healing data pipeline

A fault-tolerant ingestion pipeline that cut data loss to near-zero and made backfills a one-command affair.

GoKafkaObservabilityPlatform
View case →
Atlas — an internal design system
2024–25 Design engineer

Atlas — an internal design system

A small, opinionated component library that unified eight internal tools and halved UI build time.

TypeScriptCSSDesign systemsa11y
View case →
Field Notes — an offline-first journal
2024 Solo project

Field Notes — an offline-first journal

A tiny, local-first note app for the outdoors — no account, no cloud, works with no signal.

RustSQLiteLocal-first
View case →

Latest writing

All posts →

In praise of legible systems

The best compliment a system can earn is that a newcomer understood it in an afternoon. A short argument for legibility …

Why I still shoot film in a very digital job

Thirty-six frames is a constraint, and constraints are where attention lives. On slowness as a deliberate practice.

The two-minute deploy

How we took a deploy from twenty nervous minutes to two boring ones — and why boring was the goal.