Systems programmer. Go, C, C++ and assembly — concurrency, SIMD and the parts of
the runtime most people never have to think about. I make hot paths measurably faster,
and I write down how.
Numbers below are from the benchmarks in each repo, not estimates.
| Project | What it is | Measured |
|---|---|---|
BloomFilter Go AVX2 NEON |
Lock-free SIMD Bloom filter. Zero allocations on the hot path, 64-byte aligned, atomic CAS instead of locks. | 26 ns add · 23 ns contains 3–4× faster than willf/bloom |
SIMDCuckooFilter Go AVX2 NEON |
Cuckoo filter with hand-written assembly for bucket probing on x86-64 and ARM64. | 3–4× scalar (AVX2) 2–3× scalar (NEON) |
tributary C++20 header-only |
Many-producer → one-consumer fan-in over bounded SPSC rings. A producer never blocks; overload drops and counts instead. | 22–29 ns push, flat from 4 to 32 threads 3.87× throughput at 4 consumers |
CFD C11 OpenMP CUDA |
2D/3D incompressible Navier–Stokes solver. Multigrid, RANS turbulence, four backends. | Validated against Ghia lid-driven cavity, Taylor–Green, and channel flow at Reτ=395 |
Also building: thermolab and wavelab — interactive bilingual (EN/HE) university physics courses running entirely in the browser on JupyterLite.
I write up the optimisation work in long form — the wrong turns included.
- The Bloom Filter Optimization Saga: The "Benign" Read That Wasn't
- The Bloom Filter Optimization Saga: A Deep Dive into Go Assembly and AVX2
- The Bloom Filter Optimization Saga: Anatomy of a Go Concurrency Bug - Part 2
- The Bloom Filter Optimization Saga: Anatomy of a Go Concurrency Bug - Part 1
- The Bloom Filter Optimization Saga: From 3 Seconds to 66 Microseconds
Level 1 — The systems check (C)
main(){int i=1801675112;puts(&i);}Reveal
hack — it prints the integer's bytes as ASCII: 0x6B636168 → h a c k.
Level 2 — The logic gate
If slow is smooth and smooth is fast, how much time is lost by rushing?
Reveal
All of it. Rushing creates mistakes, mistakes require fixing, fixing takes time.
Level 3 — The hidden flag
Somewhere on this page is a message that isn't rendered. Inspect the source, you must.
Reveal
Shell we play a game? — base64, in an HTML comment.
