Computer science engineer · Michigan
Open to internships & new-grad roles
Selected work
A phone-first scheduling app I built and host for the pizza store where I'm an assistant manager. My GM uses it to build and publish the weekly schedule.
A personal dashboard I run on my homelab for email triage, my calendar, and server stats, with a local LLM assistant that has to ask before it changes anything.
A 24/7 Ubuntu server at home running nearly 30 Docker containers, including a media server for family and friends and the backend for Howie Helper.
How I work
The demo is the beginning. I like the work after “it runs”: making behavior predictable, access deliberate, deployment repeatable, and failure recoverable.
Understand the decision, constraint, or recurring friction before choosing the stack.
Interface, data, authorization, delivery, and operations are parts of the same product.
Tests, health signals, automation, and runbooks turn a useful build into a useful system.
Working set
Comfortable moving between product interfaces, typed APIs, relational data, containerized infrastructure, and the feedback loops that keep them healthy.
Start a conversation
