Software engineer, indie hacker, food enthusiast.

I'm Ian, a software engineer and entrepreneur in The Netherlands. I'm an engineer at Mercury, a financial technology company building bank products for startups. I write about engineering, cooking, and life.

Essays

31 entries

Longer-form, opinionated writing across engineering (25), personal (5), and cooking (1).

  1. What's in the Box? A Field Guide to AI Models

    A beginner-friendly tour of parameters, quantization, MoE, context windows, and other LLM jargon.

    engineering stable
  2. Stealing from Biologists to Compile Haskell Faster

    The trick that makes GHC’s ApplicativeDo optimization faster is structurally identical to how biologists predict RNA folding.

    engineering stable
  3. Making Haskell Talk to PostgreSQL Without Suffering

    How to eliminate the three performance taxes that make database queries slow: encoding overhead, round-trip latency, and N+1 query patterns.

    engineering stable
  4. Archive: Automatic Optimal Pipelining of Redis Commands

    Archived from Informatikr (originally published January 18, 2012). Describes how the Haskell Redis client Hedis achieves automatic and optimal pipelining by combining lazy I/O with a synchronous-looking API, getting the best of both synchronous and asynchronous approaches.

    engineering stable
  5. TIL: HTTP/3 Is Not Always Faster Than HTTP/2

    Local benchmarks revealed HTTP/3 can be 50-100x slower than HTTP/2. QUIC's userspace implementation loses to decades of kernel TCP optimizations on high-bandwidth, low-latency networks.

    engineering stable
  6. What Functional Programmers Get Wrong About Systems

    Type systems verify properties of programs. Production correctness is a property of systems. The gap between these is where the interesting failures live.

    engineering stable
  7. In Praise of Control Planes, or: Why You Need a Place to Stand

    The control plane pattern (a coordinator that tells workers what to do) shows up everywhere good infrastructure exists. The concept is simple. Naming it is useful.

    engineering stable
Diagram: ideas flow through drafting and revision into stable essays, with a feedback loop from revision back to drafting IDEA DRAFT REVISE STABLE REVISION LOOP
Fig. 2 / Editorial pipeline