Full-stack developer · Application architecture
I build software that holds up in the real world.
I architect and build healthcare platforms, offline-first applications, and modern web products—then keep learning what better software can look like.
Exploring now
AI-assisted development
Selected work · 01
Resilient software for work that cannot wait on a connection.
My best work lives where architecture meets operations: people need the software to stay understandable, dependable, and useful under real constraints.
NaphCare
TechCare Go
An offline-capable medication administration application designed for reliable facility workflows across approximately 40 sites.
~40
Sites
Offline
First
End-to-end
Ownership
Architecture signal
Facility workflow
Keeps moving through unstable connectivity
Local-first state
Critical work persists on the device
Synchronization engine
Batched records reconcile when online
Versioned APIs
Clear contracts connect back to TechCare
More systems · 02—04
Different products. Different pressure.
From patient-facing access to a mature clinical platform, each product asks for a different kind of engineering judgment.
NaphCare · Patient experience
MyCare Patient Portal
A secure path for patients to request appointments, complete surveys, submit grievances, and access health information across seven active sites.
7 sites
Arizona · Wayne · Pima · Montana · New Mexico · San Joaquin · Pinellas
NaphCare · Mission-critical legacy
TechCare 4.5
Engineering inside a mature WinForms EHR where every change has to respect years of workflows, integrations, and hard-earned operational knowledge.
How I think
The screen is only the visible edge of the system.
I am drawn to application and project architecture: making responsibilities clear, keeping change affordable, and designing for the environment software actually runs in.
That currently means exploring cleaner boundaries in established systems, offline-first behavior, maintainable feature slices, and where AI can improve the development loop without replacing engineering judgment.
Boundaries
Make ownership and dependencies obvious.
Resilience
Design for interruptions, retries, and recovery.
Integration
Treat contracts and data movement as product work.
Stewardship
Leave the system easier to understand than I found it.
Exploring the craft
AI is changing my build loop.
I am actively learning how AI tools can accelerate research, prototyping, and implementation—while I stay responsible for the architecture, the tradeoffs, and the result.
Why personal work matters
Curiosity needs somewhere to go.
Personal projects give me room to test ideas, develop taste, and carry a product from a vague thought to a coherent system.
Beyond the code
The things that shape my taste.
I am a developer, builder, learner, and gamer. Games are not the whole story—but they are part of how I think about worlds, systems, discovery, and memorable experiences.
Hollow Knight
Atmosphere, restraint, and a world that rewards attention.
Elden Ring
Discovery without hand-holding and systems with real depth.
Terraria
Creativity, progression, and the joy of making your own goals.
Expedition 33
A story that stayed with me long after the credits.