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

JetBrains BlogTools

Coding-Agent Benchmarks Should Match Their Users’ Task Flows

10.20

Left: SWE-Bench Pro, where each task is a single user message, almost always a new feature or a bug fix.

Agents & vibe coding Research

Read at JetBrains Blog ↗

One letter a week, starting soon.

Latest

Coding-Agent Benchmarks Should Match Their Users’ Task Flows

Related

VoicesNew paper: Emerging trends in AI agent evaluation AI Snake Oil

SiliconAgentic AI Explores Heterogeneous Chip and Interconnect Architectures (Argonne, UIUC) SemiEngineering

GitHubArticle: From Microservices to Agents: the Next Evolution of Distributed Systems InfoQ AI

LabsBuilding trust in AI agents: A production-ready evaluation framework with Amazon Bedrock AgentCore AWS Machine Learning

LabsFour evaluation engineering lessons learned from building agent plugins Google Cloud AI

GitHubMini book: Evolutionary Architecture in Practice InfoQ AI