About the service
I am a systems programmer and work in Jai every day — Jonathan Blow's native language, designed for serious game development. If your engine, tool, or simulation needs to work close to the metal without the overhead of a managed runtime, that's exactly the task I take on. I write cache-friendly, data-oriented code, replace garbage collection patterns with explicit allocators and arenas, and profile until hot loops truly earn every cycle. Manual memory management is not a burden for me, it's the essence of the work. I actively leverage Jai's compile-time execution model. Build steps, asset baking, code generation, and lookup tables are created during compilation, so there's no need to ship a separate third-party script and nothing to break at runtime. Metaprogramming lets me generate serializers, reflection data, and boilerplate code from a single source of truth instead of manually copying structures. A typical deliverable includes a ready-to-test module, a small benchmark suite with before-and-after numbers, readable comments, and a brief note on the chosen memory strategy and its justification. I've built custom allocators, SoA-style containers, hot-reload bindings, and macro-based build pipelines. Send me the rough problem outline, target platform, and performance budget — and I'll honestly tell you upfront whether Jai is the right fit. Correctness first, then speed.
