Interface
Next / React / Three
Prebuilt app shell, client-side visual systems, animated proof media, accessibility gates.
AI systems & automation. Roanoke, TX.
Build the system. Then make it survive Saturday at 2 a.m.
I lead regional operations for an automated beverage company by day, and run a home server of local AI tools, custom automations, and apps I built myself by night. Ex-DoorDash, ex-Apple.
Inspectfleet health, release drift, image proof
BuildNext app, ops tooling, launcher releases
OperateUnraid, Docker, monitoring, rollback paths
Available for senior or leadership roles acrossAI operations / technical operations / automation systems / field systems leadership
01 — about
Systems that work after the neat diagram ends.
I have been taking things apart since I was a kid. I am still doing it. The difference is that now the things are Linux-based food robots, racks of local AI servers, and partner operations across a dozen U.S. regions.
Eight years at Apple, four at Chowbotics and DoorDash, three at Botrista — all of it was the same job: keep the hardware-software seam from tearing when something goes down in Topeka on a Saturday. The AI part is new. The pattern isn't.
02 — systems map
The stack is part of the portfolio.
Browser QA
Automation
Agents / GitHub Actions
Repeatable release work, project tracking, visual baselines, and evidence-backed deploys.
Infrastructure
Unraid / Docker / nginx
Containerized delivery, health checks, private services, reverse proxy, and local hardware.
Observability
Uptime Kuma / ops portal
Fleet status, service registry, screenshots, animated walkthroughs, and degraded-state proof.
Local AI
LLMs / image pipelines
Local inference experiments become operator workflows with inputs, outputs, and handoff notes.
Field Systems
Hardware / support loops
Food robots, kiosks, partner escalation, training, deployment, and failure-mode reduction.
03 — work
Field execution, support systems, partner operations.
Hardware shipped in
- Botrista beverage robots
- Chowbotics Linux kiosks
- Apple service hardware
- homelab x86 + Pi fleet
Manager, Regional Sales Operations
I run field operations and technical deployment for Botrista's automated beverage systems across multiple U.S. regions. I am the primary contact for partner accounts when something breaks or needs to scale, and I lead training for the Sales Operations & Engineering team.
3k -> 7kcups/day on managed accounts
Partner Operations Manager
Owned the operational relationship with our largest partner accounts. Built process automation that cut deployment time and partner escalation volume, and designed the IT onboarding and offboarding programs the team still uses.
0corporate escalations
Product Support Manager
Built and led the global support function for a fleet of Linux-based robotic salad kiosks. Stood up 24/7 international support, built the third-party repair network, and designed proactive outreach that reduced cold-bowl downtime by 80%.
80%downtime reduction
Genius, Channel Service Support, AppleCare
Eight years across Apple's service organization. I worked the Genius Bar, provided remote training to Apple Authorized Service Providers, and learned how to debug a broken thing in front of a frustrated human.
8 yrsservice discipline
04 — projects
Four projects. Each one shipping.
live ops system
SlurpNet
A private network of game servers and a custom launcher I run for friends. Mods auto-update, servers self-heal, and every release is verified before players see it.
- feed coherence
- release gates
- live health
Desktop launcher app, automated releases, home-server infrastructureOpen SlurpNet dossier
brand system
Low Noise Industries
A personal brand for the infrastructure-heavy work I do. The look and feel of this site comes from it.
- visual system
- container deploy
- browser QA
Brand system, visual identityOpen site dossier
in progress
OffScript
A side project for turning prompts, notes, and operational workflows into reliable tools that someone else can run tomorrow.
- prompt specs
- operator handoff
- local docs
Prompt libraries, workflow tools, local-first docsOpen automation dossier
in development
Bloom
A side project: a game built in Unity. Procedurally-generated worlds, resource gathering, faction politics, plus the developer tools to keep it understandable as it grows.
- world loops
- simulation tooling
- systems maps
Unity, world generation, game systemsOpen systems dossier
05 — artifact wall
Screenshots are not decoration. They are proof surfaces.
artifact / 01
Ops portal walkthrough
A live-style operating surface for service groups, ports, dependencies, incidents, and recovery posture.
- animated capture
- registry detail
- incident view
artifact / 02
Launcher as release surface
The desktop app proves the messy part: feeds, game detail, channels, command palette, and release state.
- launcher UI
- release coherence
- player path
artifact / 03
Public fleet status
Health is visible, degraded states are honest, and the proof media now holds instead of looping through a false flash.
- status page
- MP4 only
- no loop flash
06 — case studies
Four case studies. What broke, what I did, what changed.
Live opsLauncher, modpack, server, and health truth stay reconciled.AutomationOne-off AI/operator work becomes a logged workflow.Field systemsFailures turn into training, process, and support systems.Deploy proofThis site proves the release habit it describes.
01 — operations proof
SlurpNet — operations under load.
Launcher, modpack, and server truth stay coherent before players see them.
problem
Game servers break when the launcher, the mod files, and the live servers stop agreeing with each other.
actions
- Built a release workflow where every change is tested, deployed automatically, and verified on the live servers before being marked done.
- Treated 'what we say is live' and 'what is actually live' as two different things, and built checks to keep them honest.
- Showed enough of the architecture to prove it works without exposing anything sensitive.
proof
- auto-deploys
- live health checks
- verified releases
- rollback playbooks
02 — automation proof
Automation that survives the second run.
Prompts become rerunnable operator workflows with logs and rollback paths.
problem
Most AI and automation experiments are impressive once and unreliable when repeated by another person or another machine.
actions
- Document the prompt, the workflow, and the checks so the experiment still works tomorrow, on another machine, run by someone else.
- Favor explicit inputs, logs, status checks, and rollback paths over hidden magic.
- Wire home-server tools, local AI, dashboards, and automation engines into routines that run themselves.
proof
- automated workflows
- local AI tools
- monitoring dashboards
- documented handoffs
03 — field systems proof
Field systems with humans in the loop.
Hardware-software operations scale without hiding the escalation path.
problem
Hardware-software systems fail in messy real-world contexts: partners are waiting, operators are frustrated, and clean diagrams stop helping.
actions
- Led technical deployment and escalation paths for automated food and beverage systems across partner environments.
- Built support, training, onboarding, offboarding, and proactive outreach habits around the actual failure modes teams experienced.
- Translated recurring issues into process, tooling, and communication improvements instead of treating each incident as isolated.
proof
- 3k -> 7k cups/day
- 80% downtime reduction
- 0 corporate escalations
- 8 years service discipline
04 — site proof
The site as proof of the deploy habit.
Every site change has local, browser, CI, deploy, and live-edge proof.
problem
A personal site should prove taste and operational discipline. If the deploy path or visual checks are weak, the portfolio contradicts itself.
actions
- Rebuilt the site so every change ships from code to live in under a minute, automatically.
- Added automated screenshots and live-site checks so visual bugs can't sneak through.
- Documented findings and tuned the motion system so animation enhances the site without hiding its content.
proof
- prebuilt Next app
- auto-deploy
- visual QA
- live verification
07 — home infrastructure
Self-hosted systems I own end to end.
The home server stack runs SlurpNet — sixteen game servers, a custom ops backend, self-hosted SSO, and full observability — plus media, dashboards, local AI tools, and whatever I am currently curious about. Same setup and same discipline as the tools I deploy at work.
Local AI
Local language models, image generation, and custom inference workflows running on hardware I own.
Automation
Self-hosted GitHub Actions runners and a custom ops backend driving deploys, health checks, and rollbacks across the fleet.
Monitoring
Dashboards that show what's healthy and what's misbehaving before anyone notices (Grafana, Prometheus, Uptime Kuma).
Network & security
Private DNS, password vault, ad blocker, managed Wi-Fi — the same kit a small business uses.
08 — contact
Talk to me about the role where systems need an owner.
Best fit: technical operations, automation systems, field systems leadership. Especially teams where software meets hardware and someone needs to answer the phone when one of them lies to the other.