Trent

Shipping no client-side script is usually sold as a speed optimisation. The speed is the smallest thing you get. What actually changes is the set of failures your site is capable of having.

Most canonical bugs are not tagging mistakes. They are a site accidentally telling search engines that all of its pages are the same page — and the defaults in every framework make that the easy thing to do.

Schema.org markup is usually treated as an SEO garnish you add at the end. It is better understood as a set of machine-readable promises about a page — which means the interesting question is what happens when the page stops keeping them.

Optimising for language models is mostly framed as writing for a new kind of reader. The more useful frame is that you are now writing for a reader that has to decide whether to stake its answer on you.

Putting your content in a repository looks like a tooling preference. It is actually a choice about consistency, history and who is allowed to write — and it has a specific expiry date you should decide in advance.

Your direct dependencies are a decision. Everything underneath them is a consequence — and on a typical install, the consequences outnumber the decisions by two orders of magnitude.

The value of a component library is not the components. It is the set of decisions it takes off the table — and a system that keeps saying yes to variants has given that value away.

Cloud cost is usually treated as an optimisation problem to be solved after the fact. It is more honest to read the invoice as a description of the system you actually built, including the parts you did not mean to.

A feed costs a few dozen lines, requires no keys, no versioning and no support, and gives every consumer — reader, aggregator, script or agent — the same view of your archive. Almost nobody ships one properly.

Categories, subcategories and tags look like three flavours of the same idea. They are three different promises about permanence, and confusing them is how a site ends up with two answers to what a page is about.

A calendar day and an instant in time are different types, and most date bugs are the moment one is silently converted into the other. The fix is not better formatting — it is refusing the conversion.

Autonomous agents are good at proposing changes and bad at being trusted with them. The whole design problem is putting a reviewable boundary between the two, and most setups skip it because the boundary is inconvenient.