/ Gamedev
A production timeline: the studios, the games that shipped there, and the role I had in each. Plus the engineering work most gameplay roles never touch: server infrastructure, code generation, multiplayer internals.
Designed and ran scalable multiplayer server infrastructure alone: EC2, Fargate, ECS, Lambda, API Gateway, DynamoDB, S3, VPC, ECR, CloudWatch. Game servers containerized with Docker.
Compile-time C# code generation: entity serialization and automatic listener creation. Mainly solo.
Multiplayer game engine and an anti-cheating framework for the internal games framework. Mainly solo/lead.
Two EU research projects on intelligent orchestration of cloud and edge resources (CHARITY, ACCORDION). Built the AR multiplayer game use-cases on the studio side.
Game-test management system (Angular + ASP.NET Web API) and servers-management web tools, hosted on AWS.
Game systems in Unity and C# with ECS (Entitas) and DI (Zenject). Mobile optimization, third-party integrations (analytics, ads, IAP), plus solo engine and infrastructure work.
Hyper-casual football title published with Voodoo.
EU research on intelligent, autonomous orchestration of cloud, edge and network resources.
EU research on cloud/edge infrastructure for next-generation low-latency applications.
Shipped F2P mobile titles.
Game systems in .NET, C# and Unity. Client-side integration of multiplayer backend services, UI work, third-party integrations.
Multiplayer card defender.
Multiplatform F2P multiplayer strategy.
05 / Connect
If you're curious how all of this works together, or you want to talk about agents, devtools, or applied AI, get in touch. Happy to walk you through it.