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

GitHub BlogGitHub

From 2,500 requests to 24: Rebuilding star history without the stargazers

10.14

Maintainers look at star history to answer a practical question: did a launch, release, or event change a project’s trajectory?

Read at GitHub Blog ↗

One letter a week, starting soon.

Latest

From 2,500 requests to 24: Rebuilding star history without the stargazers

More from GitHub Blog on Accept All

GitHubGitHub’s model for secret detection: Finding more secrets with less noise GitHub Blog

GitHubGitHub Copilot app for Beginners: How to teach Copilot about your codebase GitHub Blog

GitHubHack the World: Why hackathons are still the best place to learn to build GitHub Blog

GitHubHow one bug bounty researcher chooses the features they investigate GitHub Blog

GitHubSecret protection must scale with software GitHub Blog