Cache invalidation is a distributed systems problem
The TTL is not a cache policy. It is a probability distribution, and somebody has to own it.
Start here. The clearest case for why the medium has to admit change.
The blog format never changed. The web did.
A post is still a file: written once, dated, abandoned. But the software it describes kept moving, and so did its author’s understanding of it. So a 2019 post is quietly wrong now, and the format offers no way to fix it in place.
Strata treats a post as a living, layered document. It carries a visible revision history. It renders at the depth you choose. And it accepts notes pinned to a specific sentence and to the specific revision that sentence belonged to — so an argument with a post survives the post being rewritten.
No likes, no follower counts, no trending, no algorithmic feed. If we cannot explain why something surfaced, it does not surface.
If you only read four things
All reading lists →A starting order. The third one is the one people skip and it is the one that changes how you read the rest.
The p99 is a lie you tell yourself
You cannot add percentiles. Every latency budget that does is a budget nobody is actually keeping.
Short. Read it before your next SLD.
We deleted our staging environment
Six months in. The best thing we did was delete a database nobody had ever tested against.
The seedling. Published before the author had an answer — which is the point.
A field guide to evaluating retrieval systems
Recall@k tells you if you found the chunk. It tells you nothing about whether the chunk was useful.
The long one. Has a diagnostic you can paste into a job.
Living now
A chronological feed can only tell you what is new. This tells you what is wrong — and lets you see the exact edit.
Why your embeddings are worse than you think
Dimension buys separation, not meaning. The curve flattens hard, and three pipeline bugs were costing more than the model.
Cache invalidation is a distributed systems problem
The TTL is not a cache policy. It is a probability distribution, and somebody has to own it.
The p99 is a lie you tell yourself
You cannot add percentiles. Every latency budget that does is a budget nobody is actually keeping.
Evergreen
Posts here are not finished once. An evergreen is a surface somebody is answerable for, and the revision history is the evidence.
A field guide to evaluating retrieval systems
Recall@k tells you if you found the chunk. It tells you nothing about whether the chunk was useful.
Topics
We keep no third-party analytics scripts, no ad-tech cookies and no fingerprinting. Reading telemetry is first-party, aggregate-only, and is never shown to a writer for a group smaller than twenty readers. You can erase everything we know about you in one click →