Idempotency is the only distributed systems concept you need
Not the only one. But if you only internalize one, make it this one, because it makes most of the others survivable.
page 4
older dispatches from the README archive.
Platform teams that don't get resented
Internal platforms fail for predictable reasons. The successful ones share four properties.
Open source funding: five models, honestly compared
Donations, foundations, dual licensing, open core, and hosted service. Each works for a specific shape of project.
Compression is underrated
The cheapest performance win available, ignored because it is not glamorous. Where it pays and which algorithm to pick.
The queue is the architecture
Most scaling problems are solved by making something asynchronous. Most reliability problems are caused by doing it badly.
Run the incident before the incident
Game days, failure injection, and the specific reason your untested runbook is wrong.
Python 3.15 and free-threading's second act
The GIL-free build is officially supported and the ecosystem work is the actual story. A progress report.
I/O 2026 and the assistant that lives in everything
More model, more surfaces, and a search product that keeps changing what the web is for.
Error messages are a user interface
The message someone reads at their worst moment gets less design attention than a button. Here's what a good one contains.
Build 2026 and the platform that keeps absorbing
Agent infrastructure at the OS layer, more of the developer stack open-sourced, and a strategy that has not changed in a decade.
Naming things: the actual rules
It is one of the two hard problems and it is treated as a matter of taste. It isn't. Here are the rules that hold.
Hiring juniors in 2026
The entry-level pipeline is breaking in a way that will be expensive in five years. Some of the fixes are cheap.
Search is hard and you should probably not build it
Relevance ranking is a specialist discipline. Here's the decision tree, and what to do at each level.
Migrations that don't wake anyone up
Data migrations at scale, done in a way that is reversible at every step and boring in the middle.
The three kinds of technical debt
Deliberate, accidental, and structural. They need completely different responses and everyone calls them the same thing.
Accessibility is a testing problem
Most accessibility failures are mechanical and catchable. Treating it as a specialist concern is why it doesn't get fixed.
The Cyber Resilience Act and the unpaid maintainer
Europe is about to regulate software security across the whole product lifecycle. Open source is mostly carved out, and mostly is doing a lot of work.
The retrieval question, revisited
Context windows kept growing and retrieval did not die. It changed shape. Where the line actually sits now.
The API versioning decision
URL versions, header versions, or no versions. Each is a bet on how your consumers behave, and one of them is usually wrong.
You still do not need Kubernetes
It's excellent software solving a real problem that most teams do not have. The honest threshold, and what to do below it.