I build systems, games, and the technology behind them.
Java backends, game servers, and the full stack that ties it together. I care about systems that hold up under load, gameplay that feels right from the first input, and software so seamless nobody notices the seams.
About
I am a developer who works across backend engineering, game development, and the full stack that connects them. The same habits carry across all three: clear interfaces, predictable state, honest performance work, and systems that can be changed without breaking.
Backend work teaches me to think in services, data, concurrency, and failure modes. Game work teaches me to think in loops, input, feedback, and feel. Full stack work keeps me honest about the seam between them, because a feature is only really finished when the player or the user can actually use it.
I focus on building reliable, maintainable software; designing backend systems and APIs; developing game related systems and mechanics; shipping complete products from database to interface; and solving difficult technical problems through independent projects and experimentation.
APIs, services, data models, and maintainable architecture.
Gameplay, state, interactions, and feel.
Database to interface, shipped as one working product.
Game servers, deployment, networking, reliability.
Expertise
Each area is broken into the kinds of problems it actually solves. Select a skill to see how it is applied.
Designing and building server side applications, APIs, and data driven services that stay maintainable as they grow.
Use arrow keys to move between problem spaces
Fluency
Orbital map / ratings unchanged
Select a node or the core
Node size tracks comfort level. Ratings are unchanged from the rest of the portfolio. Select the core to read the engineering principles behind it.
Projects
Real engineering work, presented as it is. Game projects, server systems, and software tools.
A self-hosted study dashboard that keeps courses, tasks, schedules, focus sessions, and journals in one place — shipped as a single container.
A prototype service for routing events between small applications with clear module boundaries.
A gameplay experiment focused on movement, state transitions, and responsive feedback.
A server side foundation for game plugins with attention to configuration and performance.
A notebook style workflow for exploring datasets and testing small machine learning ideas.
Experience
Structured to grow into professional timelines without fabrication.
I care about architecture that remains readable as a codebase grows, favoring clear module boundaries and honest abstractions over premature cleverness.
Interactive features feel better when the underlying state machines, events, and transitions are explicit and testable.
For server side work, latency, consistency, and recovery are part of the product, not afterthoughts.
I profile and address real bottlenecks, choosing boring optimizations that ship over impressive ones that do not.
Independent work
Designed and built small backend services to explore event routing, configuration validation, and data driven workflows.
Independent work
Implemented gameplay loops, state machines, and interaction experiments to test feel before larger integration.
Infrastructure
Built and maintained Java based game servers with attention to reliability, configuration, and performance.
Learning
Explored datasets, baseline models, and evaluation workflows with Python tooling.
Philosophy
Three lenses, kept separate on purpose. How a system stays correct and how a game feels good are different problems.
How software stays correct as it grows
How a mechanic earns the moment it sits in
How the finished thing gets shipped
Contact
Open to collaboration on software, game development, backend engineering, and technical projects. Reach out on any channel below, or send a message directly.
Opens your mail app with everything filled in. Nothing is stored or sent through a server.