Clear workflows
Can someone understand the path through the system without fighting the interface?
About
I started by building spreadsheet systems that modelled game mechanics, formulas, and decision rules before I had formal CS coursework. Since then, I have moved toward full-stack apps and deployment work where the system design matters as much as the interface.
I am a computer science student at the University of Hawaii at Manoa, expected to graduate in Fall 2026, building toward software engineering roles through practical, inspectable projects.
The through-line is practical systems: what I built, how I thought through it, and where the technical decisions live.
- 01
Spreadsheet systems
Built a Mage's Survival calculator with layered formulas, build comparisons, and accuracy-first verification.
- 02
Full-stack apps
Moved from static interfaces into routes, data flow, backend behaviour, and deployment.
- 03
Deployed systems
Building project surfaces that can be deployed, checked, backed up, and represented honestly.
- 04
Self-hosted systems
Shipping projects as usable public tools, with hosting, checks, and maintenance treated as part of the work.
How I judge the work
Maintainable structure
Can the project survive changes without turning into a pile of one-off decisions?
Operational reality
Can it actually be deployed, hosted, observed, and maintained after the demo works?