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

PyTorch BlogTools

Bringing ExecuTorch to Arm Cortex-M CPUs

10.15

TL;DR Deploying PyTorch models on microcontrollers has historically required converting to other framework formats, maintaining separate toolchains, and debugging cross-framework numerical…

Read at PyTorch Blog ↗

One letter a week, starting soon.

Latest

Bringing ExecuTorch to Arm Cortex-M CPUs

More from PyTorch Blog on Accept All

ToolsExtending Inductor for the IBM Spyre Accelerator PyTorch Blog

ToolsSession-Aware Agentic Inference with NVIDIA Dynamo PyTorch Blog

ToolsBuilding Spyre as a Native PyTorch Device PyTorch Blog

ToolsModernizing Table Batched Embeddings with FBTriton PyTorch Blog

ToolsEvolution of the PyTorch Media Processing Landscape PyTorch Blog