Big-O Was Never the Bottleneck. The Cache Line Was.
Two independent variables, two threads, zero shared state, and half the throughput gone. A short tour of why, in low-latency Java, the memory layout beats the algorithm.
Writing.
Every piece I publish, newest first. They live on Medium, in The Converging Line; the RSS feed (opens in a new tab) brings each one as it comes out.
-
-
Your HFT Edge Was Never C++. It's the Cable.
A vendor cost guide told me the language was the moat. A CTO I deeply respect told me what it left out — and almost none of it is code.
-
Python and Java Concurrency in 2026: Two Languages, Two Philosophies, One Problem
The GIL is finally optional. Project Loom is stable. Here’s what concurrency actually looks like in both languages today. Real benchmarks and no religious wars.
-
Project Panama: The End of JNI and the Beginning of Real Native Java
Java has had a native interop story since 1.1. It was always broken. FFM API, finalized in Java 22, finally fixes it without a single line of C glue code.
-
We Gave Claude Code Access to Our Entire Stack. Here's What the Workflow Looks Like Now.
From ticket creation to production deploy: one conversation, eight phases, zero context switching.
-
Building a FIX 4.4 LP Integration with QuickFIX/J: Every Decision That Actually Mattered
From custom DataDictionary to zero-reflection message dispatch — what the documentation doesn’t tell you about FIX connectivity in production.
-
What Kubernetes Doesn’t Tell You Until It Breaks in Production
Scaling that made things worse, self-healing that hid the real bug, and a deployment that was technically correct but left the system inconsistent. Three lessons from the field.
-
Pair Programming vs Code Review: Why the Future of Coding Is Still About Collaboration