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

Zenn (AI)Japan

A short checklist before you trust an AI code change

10.31

Why a checklist An AI assistant can draft a patch quickly. The risk is merging a change you did not really review. Three checks Intent. Restate the change in one sentence.

Read at Zenn (AI) ↗

One letter a week, starting soon.

Latest

A short checklist before you trust an AI code change

More from Zenn (AI) on Accept All

JapanFlashAttention1~4の変遷と仕組みを読み解く Zenn (AI)

Japan自律型AIペネトレーションテスターShannonを自分のPCで動かそうとして、深いところで2回連続つまずいた話 Zenn (AI)

JapanCodex Day 26徹底解説：モバイルのアカウント切り替えと保存型リセット予告 Zenn (AI)

Japan複数のAIの回答だけを集める「個人ナレッジ庫」という発想（需要テスト中） Zenn (AI)

Japan「片目だけアニメ化」はなぜ難しい？AIアニメフィルターの仕組みを分解して考える Zenn (AI)

Japan議事録のタスク抽出をGPTで自動化して分かった、社内の繰り返し作業を仕組み化する3つのコツ Zenn (AI)