About the service
I'm a systems programmer and I work in Zig — a modern low-level language built for clarity, control and speed. Most of my time is spent at the hardware level where every memory allocation is explicit and every execution path is predictable. I design code the way Zig encourages: without hidden control flow, without hidden allocations and with a memory model you can actually reason about. If a project needs a small reliable binary that starts instantly and behaves the same on any machine, that's exactly the work I love and do best.
My focus is sound manual memory management. I build code around allocators so ownership is obvious and leaks simply don't happen: I use arenas and fixed buffers where appropriate and free exactly where I acquired. I'm equally confident working with existing C code: Zig's first-class C binding lets me link against proven libraries, wrap awkward headers in a clean interface and even use Zig's toolchain as a C compiler replacement. Cross-compilation is for me a standard delivery method. From one machine I build for Linux, Windows, macOS and bare-metal architectures without fragile toolchain fiddling, getting compact static binaries without runtime surprises.
Beyond the code itself I care about the whole delivery: readable build scripts, comptime for eliminating unnecessary work not for effect, honest benchmarks and tests that cover complex edges. Whether you need a command-line tool, a performance-critical module, a native library with C-compatible API or help reducing latency in existing codebase — I'll take the task from idea to measurable result.
— System and command-line tools in Zig
— Manual memory management via custom allocators
— C binding: bindings, wrappers, library linking
— Cross-compilation for Linux, Windows, macOS and embedded targets
— Profiling and native performance optimization
— Code generation via comptime and zero-overhead abstractions
— Moving hot sections from high-level languages to native Zig
My focus is sound manual memory management. I build code around allocators so ownership is obvious and leaks simply don't happen: I use arenas and fixed buffers where appropriate and free exactly where I acquired. I'm equally confident working with existing C code: Zig's first-class C binding lets me link against proven libraries, wrap awkward headers in a clean interface and even use Zig's toolchain as a C compiler replacement. Cross-compilation is for me a standard delivery method. From one machine I build for Linux, Windows, macOS and bare-metal architectures without fragile toolchain fiddling, getting compact static binaries without runtime surprises.
Beyond the code itself I care about the whole delivery: readable build scripts, comptime for eliminating unnecessary work not for effect, honest benchmarks and tests that cover complex edges. Whether you need a command-line tool, a performance-critical module, a native library with C-compatible API or help reducing latency in existing codebase — I'll take the task from idea to measurable result.
— System and command-line tools in Zig
— Manual memory management via custom allocators
— C binding: bindings, wrappers, library linking
— Cross-compilation for Linux, Windows, macOS and embedded targets
— Profiling and native performance optimization
— Code generation via comptime and zero-overhead abstractions
— Moving hot sections from high-level languages to native Zig
