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

Sourcegraph BlogTools

Why your migration tools are failing your engineers

06.24

The bottleneck in most large-scale migrations is not the engineers or the plan. It is that the tools cannot see the whole codebase.

Read at Sourcegraph Blog ↗

One letter a week, starting soon.

Latest

Why your migration tools are failing your engineers

More from Sourcegraph Blog on Accept All

ToolsSourcegraph MCP server and a cheaper model beat a Mythos-class model alone Sourcegraph Blog

ToolsThe hidden cost of code that nobody touches Sourcegraph Blog

ToolsAutomating Security Triage with HackerOne and Deep Search Sourcegraph Blog

ToolsSecurity Automation Evolved: From SlackOps to Programmatic SIEM Triage (Part 1/2) Sourcegraph Blog

ToolsDependency prefixes are a supply chain risk: let's fix them Sourcegraph Blog

ToolsHow we're using Sourcegraph and a Slack bot to detect vulnerabilities and react quickly Sourcegraph Blog