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

The Pragmatic EngineerVoices

Building resilient AI-powered software, and planning for when things go wrong

10.13

Last week’s guest on the podcast was Sam Newman , who had released a book I’ve personally long awaited titled Building Resilient Distributed Systems .

Languages & runtimes

Read at The Pragmatic Engineer ↗

One letter a week, starting soon.

Latest

Building resilient AI-powered software, and planning for when things go wrong

Related

LanguagesPython 3.16.0 alpha 1 is now available Python Insider

LanguagesRyan Dahl: 'Why reimplement Node? It works.' JavaScript Weekly

LanguagesBun v1.4.3 Bun Blog

LanguagesDeno is joining Cloudflare Deno Blog

LanguagesPython 3.15.0 (final) is here! Python Insider

LanguagesHooking into the Go toolchain Golang Weekly