I am a systems-oriented developer with hands-on experience across game development, server infrastructure, and application engineering. I care about the fundamentals — how memory moves, how requests scale, how game loops stay smooth under load — and I bring that thinking to every layer of the stack.
I do not stop when things work. I stop when I understand why they work.
| Domain | What I Build |
|---|---|
| Game Development | Engines, physics systems, real-time rendering, gameplay mechanics, multiplayer loops |
| Server Architecture | High-availability backends, load balancing, distributed systems, real-time multiplayer infrastructure |
| Systems Programming | Performance-critical code, memory optimization, low-level tooling |
| Application Development | Full-featured desktop and web applications with clean, maintainable codebases |
// Correctness first. Performance second. Always.
// Every abstraction earns its place. Every dependency is a liability.
template<typename Problem>
Solution solve(Problem& p) {
understand(p); // Do not guess. Diagnose.
design_before_coding(p); // Architecture is cheaper to fix than code.
implement_cleanly(p); // Future-you reads this too.
measure_dont_assume(p); // Profile. Then optimize.
return ship(p);
}I am open to roles where I can work on technically demanding problems — whether that is a game studio, an infrastructure team, or a product that needs someone who thinks deeply about performance and reliability.
I work best in environments that value:
- Code that holds up under pressure, not just in demos
- Engineering decisions grounded in trade-offs, not trends
- Ownership — I would rather own a hard problem than maintain an easy one
Available for: Full-time positions, contract work, and open-source collaboration.