Expertise / Capability-based profile

The experience behind the job titles

A discipline-by-discipline view of how I design games as technical systems—from architecture and gameplay to networking, rendering, backend, delivery, and the way teams work.

01 / Overview

Broad technical depth
Architecture as the strongest discipline

What I optimize for

A strong, stable production system in which architecture, gameplay code, tools, content, QA, and team workflow preserve fast iteration as the project grows.

Where I create the most value

At the boundaries between disciplines: turning design intent into reliable systems, making client and server responsibilities explicit, aligning rendering with the art pipeline, and keeping infrastructure useful to developers.

Good architecture should ensure that the fast solution is also the correct one

02 / Directions

Eight views of
one engineering practice

01 / Foundations

Game Architecture

Whole-game lifecycle, system boundaries, modularity, isolated development, architecture rescue, and migration without project-wide rewrites.

  • New-project foundations
  • Existing-project restructuring
  • Flexy.Bricks\ToYs and Flexy.Framework
Explore this direction →

02 / Product

Gameplay & Technical Design

Core gameplay, tools, configuration models, design-rule formalization, UI/UX structure, and rapid feature iteration across many genres.

  • Gameplay systems and features
  • Game Design Information
  • Designer-facing tools and workflows
Explore this direction →

03 / Runtime

Multiplayer & Reliability

Authoritative simulation, prediction, synchronization, reconnect, offline continuity, battle flow, and fault-tolerant client/server boundaries.

  • FPS, Battle Royale, racing, sniper, battler
  • Photon Fusion, Photon Bolt, Unity networking
  • Seamless reload and reconnect
Explore this direction →

04 / Performance

Rendering & Optimization

Practical GPU and CPU optimization, shaders, batching, voxel rendering, URP Render Features, culling, and technical-art production.

  • Apple, Android, and PC constraints
  • Approximately 7 to under 100 batches
  • Rendering systems tied to art workflows
Explore this direction →

05 / Services

Backend & Server Systems

Client/server architecture, profile and matchmaking services, battle-server orchestration, data stores, scaling decisions, and technology selection.

  • ASP.NET Core and .NET
  • MongoDB, Redis, and earlier SQL
  • Akka.NET familiarity and Orleans selection
Explore this direction →

06 / Delivery

Build, Content & Tools

Reproducible local and CI builds, content-update architecture, asset delivery, editor tooling, fast direct startup, and reusable Unity packages.

  • Unity-owned build pipelines
  • Addressables, ContentDirectory, PAD
  • Developer iteration as a first-class metric
Explore this direction →

07 / Teams

Technical Leadership

Whole-product technical ownership, hands-on CTO and lead work, mentoring, production-system design, and cross-discipline direction.

  • Hands-on CTO and lead roles
  • Scrum, QA, GD, and documentation
  • Mentoring, interviews, and hiring
Explore this direction →

08 / Advisory

Consulting

Focused external help for architecture decisions, project rescue, new foundations, team capability, and production workflow.

  • Architecture audits and project rescue
  • Setup and handover
  • One-off reviews and recurring advisory
Explore this direction →

03 / Evidence

Selected outcomes
Across different kinds of games

1–2 sec

Direct startup into the required gameplay state or test case on architecture built for rapid iteration.

2–3 days

Many gameplay features in about two days and complex UI screens in two to three.

3–4 devs

A small programming team produced faster than content and configuration could be integrated.

7–<100

Complete scenes ranging from roughly seven batches to large Battle Royale maps below one hundred.

Production work spans multiplayer and single-player FPS, Battle Royale, voxel and sandbox games, racing, 4X strategy, simultaneous-turn battlers, sniper games, runners, roguelike shooters, hidden-object games, and other formats. The full resume remains the chronological source; these pages explain the engineering capabilities behind it.