20 posts found
What a large language model actually predicts
A model does not look anything up and does not decide what is true. It estimates which token comes next. Almost everythi...
Tokens, not words: how a model reads your text
Models do not see characters or words. They see tokens — and once you know how text becomes tokens, several odd behaviou...
Why temperature changes the answer, not the knowledge
Turning temperature down does not make a model more accurate. It makes it more repeatable — and confusing the two is how...
The context window is a budget, not a memory
Bigger context windows did not give models memory. They gave you a larger envelope to fill on every single request — and...
Why models hallucinate, and what actually reduces it
Hallucination is not a glitch that a better model will one day remove. It is what generation does when it has nothing to...
Choosing between a large model and a small one
Most production traffic does not need the largest model available. Routing by task rather than defaulting to the top of...
Why agents fail on long tasks
An agent that handles five steps beautifully can fall apart at twenty. The reason is rarely reasoning — it is that the c...
When a workflow beats an agent
If you already know the steps, do not ask a model to rediscover them on every request. A fixed pipeline with model calls...
What an AI agent can actually do with a design system
Given a real design system, a model stops inventing interfaces and starts assembling them. The difference is not the mod...
Design tokens are the interface AI needs
A token that only names a hex value has saved you nothing. A token that names a job tells a model which decision it is m...
Generating layouts that respect a grid
Generated layouts usually look almost right, and "almost" is where the eye catches. Most of the fix is stating the rules...
Why component names matter more with AI in the loop
A human reads a bad component name and opens the file. A model reads it and guesses. Naming quietly became an interface...