About the service
I develop low-level functional systems in Ante — a research systems language that combines functional style with manual memory management. Ante infers lifetimes at compile time, so you get the safety of a borrow-checker and the freedom of manual allocation without mandatory explicit annotations. On top of that, algebraic effects let you express I/O, state, exceptions, and async as composable first-class handlers instead of callback tangles or hidden global state.
What I do: performance-critical libraries and services, custom allocators and arenas, effect handlers for your domain, safe FFI bridges to existing C code, and a pure functional core around an imperative shell. I keep focus on predictable memory behavior, zero-cost abstractions, and code that stays readable as it grows.
How the work goes: we start with a short design phase for data model and effect boundaries, then I build iteratively with tests at each step. Ante compiles through LLVM, so I profile hot paths and tune memory placement, keeping latencies even. You get documented source, build setup, and a walkthrough so the team can maintain the project.
Ante is a young research language, so I'm honest about what's production-ready and what's experimental. If a component needs a stable runtime, I'll suggest a hybrid path. Write down the task — I'll assess it straight.
What I do: performance-critical libraries and services, custom allocators and arenas, effect handlers for your domain, safe FFI bridges to existing C code, and a pure functional core around an imperative shell. I keep focus on predictable memory behavior, zero-cost abstractions, and code that stays readable as it grows.
How the work goes: we start with a short design phase for data model and effect boundaries, then I build iteratively with tests at each step. Ante compiles through LLVM, so I profile hot paths and tune memory placement, keeping latencies even. You get documented source, build setup, and a walkthrough so the team can maintain the project.
Ante is a young research language, so I'm honest about what's production-ready and what's experimental. If a component needs a stable runtime, I'll suggest a hybrid path. Write down the task — I'll assess it straight.
