Flint, Michigan
I build and run infrastructure — servers, deploy pipelines, and the web things that sit on top of them. Marine Corps veteran, CIS at the University of Michigan–Flint, and permanently curious about how systems break.
Infantry, then infrastructure.
Linux servers, nginx, TLS, firewalls, CI and deploy automation. I like a box I can rebuild from scratch and a deploy I can trust at 2 a.m.
Reverse engineering, OSINT, network forensics, and the physical side — locks are just authentication with worse logging.
Front to back — static sites that load instantly, small services that stay up, and design systems that keep the tenth page looking like the first.
Client sites, school projects, and things built to scratch an itch.
Municipal payments concept built as a capstone project — the kind of civic software that should be boring, fast, and never lose a transaction.
A Python terminal app for options practice — live positions and greeks rendered in the shell, so the whole thing runs where I already am instead of in a browser tab.
Identity and site work for a therapy practice — logo system, colorways, and a warm, non-clinical visual language.
Campaign site and collateral for a local school millage — plain language, fast on a phone, and readable by everyone in the district.
Site and asset work for a family pavement-marking business. Photos from a phone in a parking lot, turned into something that books jobs.
Droplets, a Pi network sensor, SDR, and a rotating cast of things plugged in to see what they do. Where most of the learning actually happens.
Email is best. PGP if it matters.