A phone-first toolkit that turns five recurring store workflows into one reliable, offline-capable system for multi-store teams.
- Role
- Product design, full-stack engineering & operations
- Status
- Live · actively maintained
Computer science engineer · Michigan
Available for new-grad opportunities
I build useful
systems—and keep
them running.
Selected work
Systems with a reason to exist.
A continuously developed, private dashboard that brings system health, planning, reflection, and a local AI assistant into one responsive workspace.
- Role
- Product design, full-stack engineering & operations
- Status
- Private · in continuous development
A private infrastructure practice focused on resilient service orchestration, deliberate storage, GPU workloads, observability, and recoverable operations.
- Role
- Infrastructure engineering & operations
- Status
- Private · operated continuously
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.
- 01
Start with the work
Understand the decision, constraint, or recurring friction before choosing the stack.
- 02
Design the whole path
Interface, data, authorization, delivery, and operations are parts of the same product.
- 03
Leave it operable
Tests, health signals, automation, and runbooks turn a useful build into a useful system.
Working set
Tools in service of outcomes.
Skills and technologies
Comfortable moving between product interfaces, typed APIs, relational data, containerized infrastructure, and the feedback loops that keep them healthy.
Start a conversation