The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

PydanticTools

Why do you need traces if you already have logs?

10.26

Developers ask me this a lot: "Why do I need traces? I have logs." I asked the same question for years. The short answer: a log line records that something happened at one point in time.

Pydantic Logfire

Read at Pydantic ↗

One letter a week, starting soon.

Latest

Why do you need traces if you already have logs?

More from Pydantic on Accept All

ToolsRun Pydantic AI coding agents in E2B sandboxes Pydantic

ToolsPydantic runs on RunsOn Pydantic

ToolsThe code is the graph Pydantic

ToolsAnnouncement: Pydantic v2.14 Release Pydantic

ToolsWould you deploy an agent you don't control? Pydantic

ToolsBuilding production agents: the observability layer Pydantic