LLMs

My blog posts are 100% AI-generated

The final sentences are close to 100% AI-generated. The experiences, opinions, angles and decisions about what to publish are not. A walkthrough of a writing process built on interrogation, rejection and arguing over single lines, and why counting generated words says little about authorship.

Your model doesn't read like you do

A language model never sees your words. Text is chopped into tokens, each token gets an ID, and each ID gets a spot on a map where meaning is defined by what sits nearby. The fluency you see is built entirely from patterns in numbers.

Watermarking AI

Classifiers stopped spotting AI output once models got good. Watermarks hide a keyed statistical bias in text, images and proteins instead. But marking output is only half the job: without shared keys, nobody else can detect it.

I miss a good stick

AI made doing more almost effortless, and that is the problem. When every quiet moment becomes a chance to ask another question or kick off another agent, you trade one deep experience for a dozen forgettable hits. Work at 20x, enjoy life at 1x.

How LLMs actually work (explained like I'm 5)

An LLM does one thing: it predicts the next token. Training nudges that guess towards the right answer billions of times, attention lets it look back at the tokens that matter, and chaining guesses together turns a prediction into an essay.

How AI made me twenty times faster at making mistakes

When implementation becomes cheap, what's left? I stopped writing code, ventured into machine learning and 3D game development, and discovered that AI made me remarkably efficient at making mistakes. Fortunately, it also made me much faster at learning from them.

Relive your childhood memories, now with no bugs

As a kid, your skills could only get you so far in a game. Sometimes the game itself was the problem. AI fixed a decades-old goalkeeper bug from a short video, and the real shift is what that means for anyone with an idea.

AI needs more uncertainty

AI has a confidence problem. Human intelligence was shaped by an uncertain world, and uncertainty is exactly the ingredient AI is missing.

AI chat is a brain in a jar

Hitting a wall with AI usually means hitting the wall of the chat box, not the wall of AI itself. Give a model memory, tool access and a browser, and the interfaces we built for humans become the integration. The bottleneck stops being the model and starts being your imagination.

Your second brain knows more than you do

An AI-assisted note system captures faster than you can understand, and the gap compounds into internalisation debt: a dense graph of links attached to a thin mental model. The test of a knowledge base is not how much it holds, but how much you could still explain with the file closed.

The integration loop

Integrating a tool with Claude rarely needs an MCP server. A boring script wrapped as a named, version-controlled skill does the job, and the real value shows up when two skills combine: one tool tells you what happened, another tells you why.

The strangest hobby at the table

Writing code by hand used to be the job. Soon it will be a hobby, like woodworking or growing your own veg. What a company pays for now is judgment: knowing what to build, catching the answer that looks right and isn't, deciding when it's good enough to ship.

Your company needs more than an LLM subscription

Handing everyone an LLM subscription gives them a model. A shared, self-hosted agent gives them a configured environment with company context, connected tools, and clear boundaries. Why a company should own that layer rather than rent it, and how to start small.

Everyone has a plan until they get punched in the mouth

Coding agents made implementation cheap, but validation never got cheaper. That shift moves the bottleneck from writing code to deciding what is worth building, and the response is more autonomy and faster iteration, not more detailed upfront plans.

Pairing with a yes-machine

Pairing with an AI feels like pair programming. It isn't. There's one prior in the room, and it's trained to agree. This post makes the case for mob programming and spec-driven development as the structural fix.

Subscribe