Lead Site Reliability Engineer · Building OpenWorld
A coordination layer for civic action, plus FreeBSD, Kubernetes, and self-hosted infrastructure.
I'm a Lead Site Reliability Engineer with a decade of professional IT experience. I've been at a keyboard since I was three years old, and I've spent most of my adult life trying to understand how the layers underneath a running service actually work, from packet to process to platform.
Most of my hands-on work today sits at two ends of the same spectrum:
Kubernetes and AWS on the production side, where I run highly
available platforms for a living, and FreeBSD and networking
on the homelab side, where I run a self-built pf router and a
fleet of small services that exist mostly to keep me sharp.
The project I keep coming back to is OpenWorld, a mobile-first coordination layer for civic action. Truly open-sourcing the world: an overlay where anyone can pin a place, propose an idea, flag an issue, recognise something working, or organise a time-bounded event. People are good. Action compounds. Agency over guilt.
Before the MSP work I spent six years going up the stack the long way, IT administration at a Beverly Hills capital group, systems administration at AT&T / DirecTV, and cloud-migration leadership at a payments processor (Atlantic Pacific Processing Systems), where I led three concurrent migrations from Azure / Eukhost / Linode into a consolidated AWS environment. That route, domain controllers and Ansible fleets to AWS Control Tower and Kubernetes, is what underwrites the SRE work today.
I'm mostly self-taught but I started formal CS coursework in 2017 and finished a Bachelor's in Computer Science at Western Governors University alongside an Associate of Arts in CS, Math, and Physics from West Los Angeles College. I'm AWS-certified, a long-time FreeBSD advocate, and a committed Vim golfer.
When I'm not on call I'm usually iterating on the network, building out the FreeBSD pf router, writing about the pf rules that hold it together, or refining the NixOS configs that define everything behind it.
Looking for the longer story? The resume covers four years as a contingent SRE on an Enterprise Platforms Integration team at a top-tier technology company, plus the prior decade across payments, telecom, and financial-services infrastructure. The /now page is the current snapshot.
"I just want to help make the world a better place. An overlay over the world where everyone can propose ideas to make the infrastructure of our world better. Truly open-sourcing the world."
OpenWorld is the project I keep coming back to. A mobile-first platform where anyone can pin a place and attach an idea, an issue, kudos, or a time-bounded timer event, and connect with everyone else who cares about that same square of ground.
$ ls -lah ~/openworld/pins/
idea · proposed improvement
issue · something broken
kudos · something working, worth recognition
timer · beach cleanup · 2026-05-23 09:00
The action rails, GoFundMe, sign-ups, petitions, contact-your-rep tools, already exist. OpenWorld is the layer that lets people coordinate around them. iOS is now live on the App Store; Android in closed Play Console testing.
A mobile-first coordination layer for civic action, pin a place, propose an idea, flag an issue, give kudos, or organize an event.
Self-built FreeBSD edge router and firewall, pf, unbound, dhcpd, WireGuard. The hub of the homelab.
Personal Nix configuration for reproducible system setups and development environments.
Portainer stack for my media server - containerized media management and streaming infrastructure.
A URL runner game based on the browser URL snake game! Creative use of the browser address bar for gameplay.
Custom configuration for the Advantage360 Professional keyboard using ZMK firmware.
Configuration for my MoErgo Glove80 keyboard - ergonomic keyboard layout optimization.
At the edge of my homelab is a FreeBSD 15 box (hostname homefw)
that handles every packet coming into and out of the network: WAN router,
stateful pf firewall, recursive DNS, DHCP, NTP, and a WireGuard
endpoint. The AT&T fiber gateway is gone; an X-ONU-SFPP XGS-PON SFP+
module takes the fiber directly and slots into one of the box's 10G SFP+ ports,
so FreeBSD pulls the public IP itself. No vendor GUI, no shadow configs. Just
/etc/rc.conf, /etc/pf.conf, and a git repo.
┌────────────────────────────┐
│ AT&T XGS-PON Fiber │
│ (SC/APC, no ISP gateway) │
└─────────────┬──────────────┘
│
┌─────────────▼──────────────┐
│ X-ONU-SFPP (XGS-PON SFP+) │
└─────────────┬──────────────┘
│ ix0 (WAN, 10G SFP+)
┌─────────────▼──────────────┐
│ FreeBSD 15 (homefw) │
│ pf · unbound · dhcpd │
└─────────────┬──────────────┘
│ ix1 (LAN trunk, 10G SFP+)
┌─────────────▼──────────────┐
│ Sodola Switch │
└──┬──────────────────┬──────┘
│ untagged │ VLAN 20
UniWorld UniWork
10.0.0.0/24 10.20.0.0/24
One LAN trunk down to a managed switch, two SSIDs out at the UniFi APs, with VLAN 20 (UniWork) firewalled away from the main LAN by rule. ZFS boot environments make every change reversible with a reboot.
Subscribe: RSS feed • Newsletter
Resources: Check out my dotfiles on GitHub