About

My background is backend engineering: Python, distributed systems, APIs that had to stay up. Six years of it, on software that went to production and stayed there. That work taught me what breaks under load and what a system looks like when somebody thought about it properly.

What changed is the rest of the stack. The parts I used to need a team for, 3D art, game design, front end, test coverage, I can now do myself with AI in the loop. So I stopped scoping projects to what one backend engineer can finish and started building whole things.

Right now that means a QA agent that runs inside your coding assistant, two games in development, and the 3D art pipeline that feeds them. The art turned into its own product line once the models got good enough to sell on their own.

How I work

• Ship something that runs, then make it good. A demo that works beats a design document.
• AI does the volume. I do the judgement about what's worth building and when it's actually done.
• Production habits carried over from backend: test it, deploy it, document it.

Background

Bachelor of Computer Applications. Six years as a backend engineer before going independent.