Posts

A proof is either valid or it isn’t. A sentence either moves you or it doesn’t. The provenance of a thing shouldn’t determine its worth — but in practice, it does, almost entirely. I’ve noticed something odd happening over the past two years, and I suspect you have too. A friend shows you a video, a proof, a piece of writing. It’s good — genuinely good. You say so. Then they mention, almost apologetically, that AI helped make it. And something in the room changes. The praise you just gave suddenly feels retracted, even though nothing about the work itself has changed. Only your knowledge of its origin has. ...

Bitcoin mining turned electricity into money. Knowledge mining turns frontier compute into insights — and the ore body only gets richer as the tools get better. Ten years ago, mining meant running SHA-256 over blocks of transactions until you found a hash with enough leading zeros. You burned electricity, wore out your GPUs, and if you got lucky, you got some bitcoin. The output was economic value, extracted from nothing but computation and time. ...

The age of disposable software was supposed to arrive with AI. It didn’t. What arrived instead is worse — and harder to see. There’s a strange inversion happening in software engineering right now, and most people are too busy shipping to notice it. For decades, the constraint was supply. Good engineers were scarce, so demand for software always outpaced the ability to build it. That scarcity shaped everything: how companies hired, how products got prioritized, how “build vs. buy” decisions got made. If you wanted software, you either paid a lot for someone to build it, or bought something generic off the shelf and molded your workflow around its limitations. ...

I used to think building software was mostly about being precise. You write a function, you know exactly what it does, and if it breaks, you can trace the break back to a line of code. This is the world of classical AI—expert systems, decision trees, rule engines. It’s Newtonian. Give me the initial conditions, and I’ll tell you exactly where the apple lands. Then LLMs showed up, and the ground shifted. ...

The new safe+idempotent HTTP method that lets you ship SQL inside the request body was published with a Security Considerations section five paragraphs long. Five. So. RFC 10008. In June 2026, the IETF published RFC 10008 — The HTTP QUERY Method. It defines a new HTTP verb that sits in the gap nobody realized was embarrassing the protocol for thirty years: the gap between GET (safe, idempotent, cacheable, no body, URI-logged) and POST (has a body, not safe, not idempotent, not automatically cacheable, looks dangerous). ...