--- title: "Ready to code is a spec now" date: 2026-09-17 url: https://remiam.co.uk/notes/ready-to-code-is-a-spec tags: [Hardware, Developer Tools, AI] read_time_minutes: 5 description: "Remiam's read on Microsoft's Project Zenith, announced September 2026: why a preconfigured Windows for developers matters less than the 64GB and 250GB/s hardware floor it sets." --- # Ready to code is a spec now *Published 2026-09-17 · 5 min read · by Liam (Remiam)* Microsoft has put a memory bandwidth floor on what counts as a developer machine. The clean desktop got the headlines. The 250GB/s is the part that changes how a machine gets bought. On 4 September Microsoft announced Project Zenith on the Windows Developer Blog, a preconfigured Windows 11 experience that ships on what it calls developer-class devices. The machine arrives with the usual dev apps, languages, runtimes, source control and productivity tools already on it, and with most of the consumer clutter taken out. It lands first on AMD Ryzen AI Halo hardware, with other manufacturers to follow. The coverage went straight to the tidy desktop. Fair enough, a Windows install that does not open with a preinstalled game is a novelty. The line that actually matters is further down the spec sheet. ## A floor, not a feature To qualify as developer-class, a device needs at least 64GB of unified memory and more than 250GB/s of memory bandwidth. Microsoft is explicit about why: it wants models in the region of 30 billion parameters running on the machine itself, without a metered connection in the middle. Those two numbers do different jobs. Capacity decides whether the weights fit at all. Bandwidth decides whether the thing is usable once they do. A model that technically loads and then produces four tokens a second is a demo, not a tool. 250GB/s is roughly the point where a mid-size model stops feeling like a queue and starts feeling like an editor. We have the same setup on the Mac side of the studio, and the experience tracks. The useful change was never the model getting smarter. It was the answer arriving fast enough that you stopped switching windows while you waited. ## The cost nobody books The other half of this is provisioning, and it is a real cost that almost never appears on a project. A new machine takes the better part of two days to become useful. Runtimes, versions, keys, certificates, the one tool that needs an older SDK. Then it drifts, because every machine is configured by hand by whoever is sitting at it, and six months later two developers on the same codebase are not running the same thing. > Every hour spent making a laptop match another laptop is an hour billed to nothing. Shipping the environment with the hardware does not solve configuration drift. It moves the starting line. You begin from a known state rather than from a fresh consumer install and a long afternoon, and a known state is something you can write down, diff and reproduce. ## What we would take from it We are not about to move the studio to Windows over this, and nobody should buy a machine because the Start menu is quieter. Two things are worth copying regardless of what you build on. - Treat memory bandwidth as a purchasing criterion, not a footnote. If any part of your work runs a model locally, it is the number that decides whether that is practical, and it is the one spec you cannot upgrade later. - Write the developer environment down as a spec, the way you would a server. A machine that can be rebuilt from a document is worth more than a machine somebody remembers setting up. The interesting signal here is that a platform vendor has decided the local machine needs enough headroom to run real inference, and has put a number on it in public. For the last two years the assumption has been that serious AI work happens somewhere else and you rent it by the token. A hardware floor aimed at running 30 billion parameters on the desk is a quiet argument that some of it is coming back. ## References 1. [Microsoft, Announcing Project Zenith: the ready-to-code Windows experience on developer-class devices, Windows Developer Blog, 4 September 2026](https://blogs.windows.com/windowsdeveloper/2026/09/04/announcing-project-zenith-the-ready-to-code-windows-experience/) 2. [Engadget, Microsoft announces Project Zenith, a clutter-free Windows experience meant to entice developers, September 2026](https://www.engadget.com/2251018/microsoft-announces-project-zenith-clutter-free-windows-experience/) 3. [TechRepublic, Microsoft Project Zenith: Windows developer PCs will come ready to code, September 2026](https://www.techrepublic.com/article/news-microsoft-project-zenith-windows-developer-pcs/)