Skip to content

About

Engineering and play, treated as one craft.

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.

Backend systems

APIs, services, data models, and maintainable architecture.

Game systems

Gameplay, state, interactions, and feel.

Full stack

Database to interface, shipped as one working product.

Server infrastructure

Game servers, deployment, networking, reliability.

Expertise

Skills organized by problem space

Each area is broken into the kinds of problems it actually solves. Select a skill to see how it is applied.

Backend & Systems Engineering

Designing and building server side applications, APIs, and data driven services that stay maintainable as they grow.

8 skills

Core

Interfaces and data

Scale and performance

Use arrow keys to move between problem spaces

Fluency

Language comfort levels

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

Selected work

Real engineering work, presented as it is. Game projects, server systems, and software tools.

StudyAssist dashboard showing course stats, calendar, class list, and gallery
Full Stack Applications Self hosted study platform

StudyAssist

StudyAssist is a personal study operating system: it tracks courses and class times, manages tasks and schedules, runs Pomodoro focus sessions, monitors screen time, and stores journals, files, and galleries. An admin panel handles accounts, exports, and backups. The whole platform runs from one Docker image: an Express API and a SvelteKit SPA served by a single process, backed by a local SQLite database.

  • SvelteKit
  • Express 5
  • TypeScript
  • SQLite
  • Docker
View project Live site
Gameplay Sandbox abstract cover artwork
Game Development Gameplay prototype

Gameplay Sandbox

A gameplay experiment focused on movement, state transitions, and responsive feedback.

  • C++
  • OpenGL
A Minecraft castle build with towers and a bridge at dusk
Game Server Systems Game hosting platform

Minecraft Game Servers

A private hosting platform for Minecraft Java and Bedrock servers, run on a Linux VPS with a full web panel and per server isolation.

  • Docker
  • Traefik
  • MariaDB
  • Java
  • Linux
Model Notebook abstract cover artwork
Data Science & ML AI experiment

Model Notebook

A notebook style workflow for exploring datasets and testing small machine learning ideas.

  • Python
  • NumPy
  • scikit-learn

Experience

Engineering highlights and independent work.

Structured to grow into professional timelines without fabrication.

Systems that stay understandable

I care about architecture that remains readable as a codebase grows, favoring clear module boundaries and honest abstractions over premature cleverness.

Gameplay built on predictable state

Interactive features feel better when the underlying state machines, events, and transitions are explicit and testable.

Multiplayer reliability as experience

For server side work, latency, consistency, and recovery are part of the product, not afterthoughts.

Performance measured, not guessed

I profile and address real bottlenecks, choosing boring optimizations that ship over impressive ones that do not.

  1. Independent work

    Backend prototypes

    Designed and built small backend services to explore event routing, configuration validation, and data driven workflows.

    • Java
    • Python
    • PostgreSQL

  2. Independent work

    Game systems prototypes

    Implemented gameplay loops, state machines, and interaction experiments to test feel before larger integration.

    • C++
    • State machines
    • Input handling

  3. Infrastructure

    Game server platforms

    Built and maintained Java based game servers with attention to reliability, configuration, and performance.

    • Java
    • Linux
    • Networking

  4. Learning

    AI and ML experiments

    Explored datasets, baseline models, and evaluation workflows with Python tooling.

    • Python
    • NumPy
    • scikit-learn

Philosophy

How I build, and what I refuse to trade away.

Three lenses, kept separate on purpose. How a system stays correct and how a game feels good are different problems.

System Design

How software stays correct as it grows

  • Build systems that remain understandable as they grow.
  • Prefer maintainable architecture over unnecessary complexity.
  • Model the domain before reaching for the framework.
  • Make failure modes explicit before they happen.
  • Treat multiplayer reliability as part of the player experience.
  • Optimize real bottlenecks rather than chasing meaningless numbers.

Game Design

How a mechanic earns the moment it sits in

  • Make gameplay feel intentional and systems behave predictably.
  • Tune the loop before polishing any single frame.
  • State should be explicit, never implied by scattered flags.
  • Design the failure state as carefully as the winning state.
  • Good game feel is responsiveness, not complexity.
  • Play it early and often, then let the test decide.

Craft

How the finished thing gets shipped

  • Build things people can actually use and experience.
  • Ship working software over perfect plans.
  • Take the unglamorous parts seriously, they are most of the product.
  • Measure what matters and ignore vanity metrics.
  • Own the problem end to end, not just your slice of it.

Contact

Let us build something that matters.

Open to collaboration on software, game development, backend engineering, and technical projects. Reach out on any channel below, or send a message directly.

Send a message

Opens your mail app with everything filled in. Nothing is stored or sent through a server.