// writing · data lakes, platforms, quality, AI agents
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.
System designVertical vs horizontal scaling, explained simply
A bigger machine or more machines. Both work, and the choice changes how you build.
System designCaching 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.
Data lakes and query enginesRegister 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.
EssaysExplaining 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.
Data lakes and query enginesTrino 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.
Data lakes and query enginesMaking 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.
AI agentsA 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.
Data qualityHow 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.