About
About
I am a systems and product engineer working in Elixir and C3, building libraries, protocols, and the products on top of them.
I’m a systems and product engineer. Most of my work is in Elixir and C3, with TypeScript and Rust when the problem calls for them.
I work on the layers a product stands on: an HTTP stack for C3, the async I/O library underneath it, tree CRDTs for collaborative editors, a native UI toolkit, a browser CAD kernel. Then I build products with those pieces — a Spotify client, a trading platform, an archive of public documents. The through-line is the same: read the spec, keep the interfaces small, and make the failure modes explicit.
What I’m working on
- Shekl — browser parametric CAD with a B-rep kernel in C3 and an AI that co-edits the same document.
- Glaze — a native Spotify client for Linux, and the reason Kiln exists.
- c3web and c3io — HTTP and async I/O for C3, built to run in a server or a game loop.
- Jaari and Sinag — two very different data problems: markets, and scanned public records.
Day to day
I work on NectarineCredit’s platform: Elixir, Phoenix, GraphQL, and a React client. Trade credit is unglamorous in the best way — money moves, audit trails matter, and the database has to agree with the ledger.
How I work
- Specs before abstractions. A protocol, a CRDT, or a file format is worth reading properly once. The bugs you avoid are cheaper than the ones you fix.
- Small libraries, sharp edges. A library should do one thing and say what it does not do. The README is part of the interface.
- Tests are design. Conformance suites and failure cases tell you whether the abstraction is real; happy-path tests only tell you it compiles.
- Native where it counts. Not everything needs a browser. When a desktop application or a kernel is the right shape, I would rather write it than wrap it.
Elsewhere
The code is on GitLab and GitHub; the published Elixir packages are on Hex. The archive lists everything else, including the experiments.