Web Application
Grind City Empire
Systems design and interactive product engineering proof point
Developed a browser-based interactive system with persisted state, upgrade/economy mechanics, modular stores, and richer product logic.
Problem
Interactive products with progression systems require more than CRUD; they need complex state architecture, persistence, and balancing logic.
Outcome
Highlights systems design ability, complex state handling, and thoughtful product engineering under richer interaction models.
Approach and Solution
Built a browser-based interactive system with persisted state, upgrade/economy mechanics, and modular frontend architecture.
Needed modular stores, progression mechanics, multiple screens, and maintainable testable logic in a richer UI environment.
Architecture Notes
React + TypeScript + Zustand persistence + React Query + modular screens, supported by Vitest configuration for stronger engineering discipline.
Security: Not security-heavy by nature, but benefits from maintainable modular architecture and testable business logic.
Performance: Interactive responsiveness and state coherence are central to the experience and engineering quality.
Lessons and Next Improvements
Balancing and progression systems are a strong proof of systems thinking when documented clearly with architecture notes and tests.
Add README/how-to-run, screenshots, systems-design write-up, and stronger proof around testing coverage and gameplay loop quality.
Outcome Metrics and Signals
test_coverage
placeholder
% · current · test runner
Media and Visual Proof
Related Build Notes
Career Journey
From Information Systems student to product-minded engineer
My growth came from combining formal Information Systems study with freelance shipping, system design, and practical automation work.
Continue through the journey with timeline context or view the full resume page.