Operator profile
About
Who I am, what I work on, and how I got here.
I write software that other people depend on. That means I care less about clever code and more about boring reliability, clear interfaces, and systems that fail loudly instead of silently.
## What I do
Most of my work sits at the intersection of systems programming, platform engineering, and developer tooling. I build the parts of the stack that nobody notices until they break, and I try very hard to make sure they never break.
That usually means Rust or Go for performance-critical paths, Python for automation and glue, TypeScript when the work touches a browser, and Terraform when the work touches a cloud.
## How I work
Small commits. Honest commit messages. Tests that actually run in CI. Documentation written for the next person, not for me. If a system needs a runbook, the runbook ships with the system.
## Background
I started with Python scripts that automated the boring parts of other people's jobs. That turned into backend systems, then infrastructure, then a habit of building tools whenever I hit the same problem twice.
2026
Independent systems work
Contracting on infrastructure, developer tooling, and reliability. Writing in public.
2024
Platform engineering
Owned CI/CD and deployment pipelines for a distributed team. Cut deploy time from 40 minutes to 6.
2022
Open source tooling
Started releasing the utilities I was building for myself. Some of them stuck.
2019
Backend engineering
Shipped production APIs and data pipelines. Learned that uptime is a feature you design, not hope for.
Proficiency
Python
94%
Rust
82%
TypeScript
88%
Go
76%
Terraform
84%
PostgreSQL
80%
Colophon
This site is built with Jekyll and hosted on GitLab Pages and GitHub Pages. It uses IBM Plex Mono and IBM Plex Sans. There are no photographs on the home page, by design. The aesthetic is the point.