Software engineer · Explorer at heart
Exploring complex systems. Building reliable paths.
I enter unfamiliar systems, find the signal, and turn what I learn into software people can trust.
Concept build · Profile, career, project, and contact details are mock data.
I turn curiosity into systems that hold up in the real world.
From game systems to cloud platforms, every project is a map of what I questioned, tested, shipped, or learned the hard way.
Three trails. Three kinds of evidence.
Wins prove execution. Failures prove judgment. Experiments prove curiosity.
Platform Engineering
Signal Atlas
OutcomeThe mock pilot reduced the median path from alert to suspected service and gave responders one shared source of context.
Product Experiment
Northstar Scheduler
TakeawayAutomating a decision before understanding its emotional cost creates faster rejection, not better planning.
Systems Experiment
Relay Edge
OutcomeThe experiment identified a narrow class of routing decisions worth moving while keeping stateful logic centralized.
Open the complete expedition log · 14 projects
Explorer mindset. Engineer discipline.
My game-industry roots taught me to care about feedback loops, edge cases, and the person holding the controller. Today I bring that same instinct to backend, platform, and product engineering.
INVENTORY
Java / Spring Boot / Node.js / PostgreSQL
AWS / Kubernetes / Docker / Argo CD
React / TypeScript / Accessibility / Motion
System Design / Observability / Testing / Writing
FIELD RULES
- 01Make systems observable.
- 02Prefer reversible decisions.
- 03Treat failure as evidence.