Who’s writing
I’m a software engineer at a high-frequency trading firm. I’m still learning constantly, and I write these posts to summarise what I pick up: partly to cement it for myself, partly because I’m happy if they help someone break into the industry.
What this blog is
Deep dives on the systems, languages, and tools that make latency-sensitive software work, and the broader ecosystem they sit in. Some of it is JVM-internal (ZGC, JIT, Loom), some of it is data-shaped (DuckDB, ClickHouse, Iceberg), some of it is networking and OS (kernel-bypass, eBPF), some of it is the trading-domain mental models I wish I’d had on day one (order books, single-writer designs, market microstructure).
Posts are deep, opinionated, and skewed toward what’s actually useful to know vs. what shows up in marketing material. Where I haven’t measured something I’ll say so. Where a “best practice” is mostly cargo-cult I’ll say that too.