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

LobstersGitHub

Pair-coding Lobste.rs feat

10.28

There is a long standing issue I'm working at that turned out to have some interesting refactoring suggested by the admins . Does anybody want to pair-code this feat with me?

ruby meta ask

Read at Lobsters ↗

One letter a week, starting soon.

Latest

Pair-coding Lobste.rs feat

More from Lobsters on Accept All

GitHubMaking SIMD Code Scale to Any Vector Width Lobsters

GitHubRaspberry Pi Zero 3 W and Pi 4 Model A on the Way? Lobsters

GitHubForging a Microsoft Edge Full Chain with Logic Bugs Only Lobsters

GitHubCode-execution flaw in UEFI firmware affects most servers on planet Earth Lobsters

GitHubA fast and secure tar parser for the Rust ecosystem Lobsters

GitHubPython's experimental JIT to be removed Lobsters