About
Two practices, one instinct: figure out how a system actually behaves, and make it run. Software, networks, an ECU, a body in training — same loop of observation, hypothesis, repair.
bio · — to be added
01 · Story
01 · The through-line
Curiosity has always pulled in two directions: how software systems behave, and how physical systems behave. The software side started with computers, networks, and Linux; the mechanical side started with engines, tools, and the smell of brake cleaner. Both turned out to be the same skill in different uniforms — read the system, form a model, test the model, repair or replace.
02 · Where the two meet
Engineering work rewards people who can hold a long horizon and a short one at the same time: the long horizon of a system designed to last, the short horizon of the next commit, the next bolt, the next recovery run. The longer I work, the less difference I see between a clean codebase and a clean shop floor.
03 · What came before
The path that brought me here ran through generalist roles — picking up whatever the project needed and getting good enough to be useful. That habit stuck: read the manual, do the work, leave it documented, repeat.
— anchor TBD · to be added
04 · Open-source first
I default to open-source because it gives me four things at once: transparency (I can read the code I run), ownership (I can fix it without permission), community (the work compounds across thousands of strangers), and no lock-in (I can leave when the tool stops serving me). Where a proprietary option is genuinely better, I pair it with the open alternative so the choice stays mine, not the vendor's.
02 · Mechanics & Garage
Software pays the bills. The garage keeps the mind honest.
Working on cars teaches the same things engineering does — diagnostic discipline, the patience to read before you act, and the humility to admit when the manual is right and you are wrong. Most of the work is logical: scan, test, isolate, fix. ECU, immobilizer, cluster adaptation, wiring — the satisfaction isn't in the parts, it's in the loop closing.
specific garage & tools · — to be added
03 · Motorcycles & Travel
Two wheels, long roads, slow input.
Motorcycles and travel function the same way: pull the input rate way down, let the system think, and pay closer attention to what comes back. Routes are picked for character, not efficiency. The point isn't the destination — it's the hours of uninterrupted attention a road demands, and the ideas that surface when the screen goes away.
defining routes · — to be added
04 · Philosophy
Stoic framing, applied without ceremony.
The Stoics left a working toolkit: distinguish what you control from what you don't, and spend your energy on the first; act with virtue as the only thing that is fully yours; treat obstacles as the material of the work, not its interruption. None of it is exotic — it's the same engineering discipline applied inward. Read more on it under the writing index.
01 · Dichotomy of control
Sort cleanly between what is up to you (judgment, effort, attention) and what isn't (outcomes, weather, other people). Operate on the first; release the second.
02 · Virtue as craft
Treat integrity, judgment, and care as the four cardinal skills of the trade — the things that compound no matter what the project is.
03 · Amor fati
Don't just endure friction; use it. The same logic that says 'the bug is the lesson' says 'the traffic, the deadline, the blown gasket — also the lesson'.
Source · Stoic tradition (Marcus Aurelius, Epictetus, Seneca)
Read the stoicism writing05 · Now / Toolkit
A live snapshot — fill it in, update it when it changes.
01 · Focus
· TODO(personal): current focus — the one project or theme dominating the next quarter.
02 · Reading
· TODO(personal): current reading — a book, paper, or long-form piece you're working through.
03 · Training
· TODO(personal): current training block — e.g. a strength cycle, a metcon focus, a recovery week.
04 · Tools
· TODO(personal): current toolchain — the editor, the stack, the bench tools.
05 · Default toolkit · open-source first
The stack I reach for first — open-source by default, swap on reason. Replace any line with your current tool of choice.
Linux01Proxmox VE 9 hypervisor on bare metal, Debian 13 / Ubuntu LTS servers and workstations — Fedora and CentOS Stream in the mix.
Docker02Docker Engine + Compose v2 as the unit of deployment for every service — Apache-2.0 open core, no desktop licensing.
Python033.14 as the default for automation and backends — pip/venv for the standard path, uv for speed.
JavaScript04TypeScript + Node.js 24 LTS for web and agent work — Next.js on the front, npm ecosystem behind.
PostgreSQL0518 as the relational core — pgvector for embeddings, Drizzle ORM on top.Update cadence · quarterly · edit src/lib/about.ts
06 · Gallery
A handful of frames from the garage, the road, the gym, and the bench.
07 · Credentials
Degree and coursework — every one of these can be checked against the issuer's own registry.
/contact
AI systems, ECU work, motorcycles, training — pick a thread. I read every message and reply within two business days.
