Skip to content
Writing

// writing · data lakes, platforms, quality, AI agents

System design

What a load balancer does, explained simply

One address for your users, many servers behind it, and a quiet check that keeps broken ones out of the way.

21 November 2026
System design

Vertical vs horizontal scaling, explained simply

A bigger machine or more machines. Both work, and the choice changes how you build.

21 November 2026
System design

Caching 101: where a cache sits and what it saves

A cache is a copy kept closer to where it is needed. Every layer you add skips some of the trip.

21 November 2026
Data lakes and query engines

Register Iceberg tables in a Postgres catalog for faster Trino queries

A small Postgres database, two tables and one row per Iceberg table took my Trino lookups from 13 seconds to under one.

21 November 2026
Essays

Explaining a data platform decision to people who don’t write SQL

The numbers were right. The unit was wrong, and an analogy did more work than any chart.

21 November 2026
Data lakes and query engines

Trino vs StarRocks vs Doris on an Azure Iceberg lake

Same tables, same machine, same six questions. One engine was fastest, one was most familiar, and one couldn’t read the files at all.

20 November 2026
Data lakes and query engines

Making a Trino lake as fast as a SQL database

Most of the slowness wasn’t the engine. It was the questions the engine asked before it started.

19 November 2026
AI agents

A brake for Claude Code on Azure: ask before anything that costs money

My approval was a sentence in a chat window. The storage account it allowed was real, and billing.

19 November 2026
Data quality

How my data checks lied: a row count passed with damaged bytes

One day of Wikipedia pageviews on one laptop, and the nine failures that showed which checks to trust.

18 November 2026