Game development, software,
AI, and security

I build games and their backend systems, developer tools, and AI/ML prototypes, and review security and performance. Work can start from scratch or fit into a project you already have.

Start with what you need

From brief to implementation

Before I write any code, we agree on what to build and how to check that it works. The handover follows that agreement.

Describe the feature

Send the goal, an example flow, the platform, and any existing code. For a bug, include the steps to reproduce it.

Agree on scope

We list the work, dependencies, priorities, timeline, and what counts as done, so nothing is left to assumption.

Build & check the flow

I build and integrate the feature, then test how it handles normal use, cancellations, bad input, and disconnects.

Hand over with context

You get the source code, integration steps, configuration notes, test results, and any limits that remain.

Before we start

Yes. I read through the existing code and how its parts depend on each other before adding or changing anything.
Send a brief first. Estimates depend on the feature, complexity, existing code, and integration needs. We agree on scope and timeline before work begins.
Yes, on the scripting side: UI controllers, input, feedback, and integrating animations. In Bentengan I designed the Match Found screen that appears when a match is ready, and reworked the basic attack animation (hit/M1). New art or animation made from scratch is agreed separately in the brief.
I work on games in Roblox, Unity, or Godot, and build software and developer tools with Python, TypeScript, Go, or Rust. I also make AI/ML prototypes with PyTorch or TensorFlow and review security. If your stack is not listed, include it in your brief and I will let you know whether the project is a good fit.

Describe what you need,
and we’ll work out the scope

A goal, platform, example flow, and rough timeline are enough to start a conversation.

Send a brief