The first hour after a provider announcement
Most of the work in the hour after an announcement is reading, in a fixed order. Here is the order, and how each answer maps to one of four recommended actions.
Four categories: what providers shipped and what to do about it, how the evaluation work is actually done, which tools fit which job, and public post-mortems of AI features going wrong, with sources.
Every number here carries a source id. Every provider statement traces to a change log entry with the provider's own announcement.
20 posts
Most of the work in the hour after an announcement is reading, in a fixed order. Here is the order, and how each answer maps to one of four recommended actions.
A gate on every pull request changes review, deploy timing and who argues with whom. Here is the practical shape of it, and the class of change it cannot catch.
Pricing and context-window entries look like finance news. They land in chunking, truncation and cost logic that somebody tuned once and never revisited.
A deprecation notice is a dated commitment from one company about one platform. Here is what Anthropic, OpenAI and Google each publish, and how to plan against it.
Reference based scoring needs an expected result stored next to the input. When none exists, what replaces it is a written rubric, reference free scorers and a labelled sample your own expert graded.
The thing that ages an eval dataset is usually not a model release. It is your own users, asking things the set was never built from, while every run keeps passing.
Elsewhere on the site