🌡️ Content is a Dish Best Served Cold

Not all content runs at the same temperature.

Cold content never changes. A blog post. A release tarball. A build artifact. Serve it from a CDN, cache it forever, scale it infinitely for free. No framework required — just a file.

Warm content changes occasionally but not collaboratively. Your login state. A prerendered component. A report that finished five minutes ago. One writer, many readers. It can be cached, served from the edge, refreshed when it changes.

Hot content is genuinely live. Multiple writers, simultaneous edits, real conflicts. A shared document. A trading order book. Hot content needs real infrastructure — CRDTs, consensus, the works. It's hard and expensive and worth it — for the small surface that's actually hot.

The default web stack runs everything hot. Request in, database query, template render, response out — for every request, even the ones asking for the same thing the last ten thousand requests asked for. The cache gets bolted on afterward, when you notice it's slow.

The irony is that social media — the industry most associated with "dynamic" content — is mostly serving cold assets. Your feed is JPEGs and text. But they brought the heat anyway. And not for nothin'. Their business is tracking. Every request is intelligence about you, funneled into your definitive psychological profile, all with the goal of training you to salivate. Keep you hot under the collar and the metrics improve. Another penny of value extracted.

Cold isn't boring. Cold content can be almost anything, and you can always warm it up if needed. A cold HTML page is a program — it can do anything a browser can do. Hot is often the boring one. A Facebook post cannot be a program, cannot run code, cannot be an interactive game or dataviz. They give you television and newspaper. Not the hypermedia we were promised.

Content is a dish best served cold.