I work across backend systems, game development, integrations, and the kind of engineering problems that sit between architecture and delivery. The through-line in my work is practical software: code that can be evolved, handed over, and trusted in real production contexts.

My recent experience spans professional game programming and enterprise delivery. That combination matters because it builds two useful instincts: the need to ship under real constraints, and the discipline to keep systems maintainable even when the surrounding product or organization is messy.

I am especially interested in game-adjacent backend systems, data movement, integration boundaries, and the engineering tradeoffs that appear when multiple teams or disciplines need the same software to behave differently.

Outside the strongest professional material, I still value smaller technical work in graphics, compilers, and systems programming. Those projects remain useful because they keep the fundamentals close: how software behaves under the abstractions, and where complexity really comes from.