Build systems that stay readable¶
Engineer focused on delivery infrastructure, team enablement, and secure remediation workflows that help teams move without guesswork.
Operating System
Calm tools for high-pressure teams¶
I build documentation and delivery systems that make the next action obvious: setup paths, release loops, quality gates, and agent handoffs that are easy to inspect.
- Readable by defaultClear structure before clever automation.
- Built for handoffEvery workflow leaves context for the next maintainer.
- Low-maintenance designReusable Zensical primitives instead of page-by-page styling.
Currently¶
- Finishing a B.S. in Computer Science while shipping production systems at Fiserv.
- Standardizing delivery practices across teams: CI/CD, docs-as-code, and repeatable vulnerability remediation.
- Building Terminal Jarvis — a unified CLI for orchestrating multiple AI coding assistants.
What I Build¶
I work on the layer that makes teams feel faster: the defaults, pipelines, and docs that remove friction before it becomes process.
- Delivery infrastructure with predictable setup and repeatable release paths
- Docs-as-code systems that lower onboarding and support cost
- AI-assisted workflows with practical guardrails and clear handoffs
- Remediation patterns that move security from heroic effort to team habit
How I Work¶
Marine Corps veteran turned engineer. I value quiet systems, clear ownership, and interfaces that explain themselves on the first pass.
Currently focused on making teams self-sufficient: turning tribal knowledge into documented defaults, one-off fixes into repeatable workflows, and manual steps into automation that is easy to inspect and maintain. Based in Omaha, Nebraska. Bilingual in English and Spanish.
Featured Work¶
-
Terminal Jarvis
A single CLI for orchestrating Claude Code, Gemini CLI, GPT, and adjacent tooling without changing the team workflow every week.
-
Coder Infrastructure
Self-hosted Coder templates and bootstrap scripts that make a fresh workspace feel consistent on day one.
-
Docs-as-Code Platform
This site as a working system: Zensical builds, versioned docs, release automation, and deliberate information architecture.
-
Interface Experiments
WebGL studies, visual prototypes, and layout experiments used to test motion, contrast, and interaction quality.
Working Principles¶
Documentation should lower hesitation.
I write for the next person who has to ship under time pressure.
Predictable beats clever.
Reliable pipelines and visible failure modes are worth more than flashy automation.
Infrastructure is a product surface.
Teams deserve sane defaults, readable controls, and change paths that are easy to reason about.
Motion should support meaning.
I use animation and interface detail to orient people, not to compete with the content.
Let's Talk¶
Available for collaboration, consulting, and conversations about developer experience, platform work, and documentation systems.