Lobsters: latest AI & code stories | Accept All

Skip to content

Accept All すべて承認 /

Lobsters

13 stories

LobstersGitHubTerence Tao on “prematurely solving [a maths] problem by purely AI-powered methods” I recommend reading the whole thread, but I linked to the part I found the most relevant. I believe the same is true for programming. Comments

LobstersGitHubDebian Code Search: Fast TurboPFor with Go SIMD Comments

LobstersGitHubThere's No Limit to How Bad Code Can Get Comments

LobstersGitHubM2: Episode 1 (or, Asahi Linux on M3) Comments

LobstersGitHubLarge-Language Models as a Cognitive Virus Large-language models (LLMs) are rapidly becoming part of human culture, reshaping how information is produced, transmitted, and used. Here we propose that their diffusion can be understood through a viral analogy, with

LobstersGitHubWhat filesystem are you running on your NAS/Backups, and why? What filesystem are you running on your NAS/Backups, and why? And if you're using multiple disks/devices, how do you manage them (filesystem's RAID, mdadm or other software solutions, hardware RAID)?

LobstersGitHubPointing at the error: compiler-style diagnostics in uutils coreutils Comments

LobstersGitHubRust SIMD on the GPU Comments

LobstersGitHubTrusting-Trust Attack against an Entire Linux Distribution (via the strip utility) "Ken Thompson's trusting-trust attack, in which a compromised compiler backdoors the programs it builds and reproduces the backdoor in subsequent rebuilds of itself, is widely regarded as a threat specific to compilers.

LobstersGitHubBespoke: A Programming Language for People Who Say Please Comments

LobstersGitHubIs it too much to ask devs to use AI to review their hand-crafted code? You believe coding by hand is the Way and I both admire and appreciate beautiful, hand-crafted code. But I want to use your library, and when I ask my AI to evaluate it for bugs, memory leaks, security issues, it returns

LobstersGitHubIs AI ruining my brain? Comments

LobstersGitHubSurviving Code Reviews in the era of AI My coworkers are all fully AI pilled. As a consequence, every PR that comes my way for review is on average ~6k lines of diff. It's well established that even PRs an order of magnitude smaller than this are too big to be

On the calendar

予定 · Conferences and launch events, this week's stories from each corner of the industry, and what its press is covering — in English

On view

This week, from that corner the newest stories from the corner of the industry you picked

The wire their own posts, translated

How code moves in 2026 from the industry's own reports

Sources

Fetched every three hours, linked to the original

About

Accept All is a magazine, a radar and a diary about artificial intelligence and the craft of code — read from Tokyo, for people who build.

The name is the button. Code is written by agents now and reviewed by a human thumb that hovers over Accept all a hundred times a day; the whole question of this decade is what, exactly, you just accepted. So we read the diff. A magazine, because every week one model, one tool or one idea is worth reading about slowly. A radar, because we count what the labs, the Valley, GitHub and the chip makers are talking about — releases, agents, open weights, compute, funding, rules — and show it as it moves. A diary, because a seal is set each day in that day's colour, and the days add up.

We read the research labs' own posts, the American and European tech press, the Japanese and Chinese developer sites and the newsletters people actually forward, and bring it together in English and Japanese. Everything here links back to the people who wrote it; the images belong to their authors.

Accept All will keep changing. New sources, new signals, new ways of looking — a little better each week, never finished. If something here made you open a terminal, that is enough.

Thank you for reading. ありがとうございます。