Build systems that stay readable¶
Product-minded engineer focused on developer tooling, docs-as-code, and delivery systems that help teams move without guesswork.
What I Build¶
I work on the layer that makes teams feel faster: the tooling, pipelines, and docs that remove friction before it becomes process.
- Developer platforms with predictable setup and useful defaults
- Docs-as-code systems that ship with the product
- AI workflows with guardrails, observability, and clear handoffs
- Delivery pipelines built for repeatability, not drama
How I Work¶
Marine Corps veteran turned engineer. I value quiet systems, clear ownership, and interfaces that explain themselves on the first pass.
Currently finishing a B.S. in Computer Science while shipping production systems. 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.