Hey, I’m Ram. AI and chips, explained from the factory floor.
This weekMES & Shop-Floor Systems2:00
AI Data Centres Can Pause. A Chip Factory Never Can.
3 AI Power Moves, 1 Week, and a Rule Chip Factories Wrote in 2000. The mechanism underneath it, the number that makes it real, and where I could be wrong.
This week’s story
Everything, 48 pieces
3 AI Power Moves, 1 Week, and a Rule Chip Factories Wrote in 2000
The AI boom ran out of power three times this week, and a chip factory wrote the answer in the year 2000. On 16 September 2026 the US House of Representatives voted 417 to 3 for the Ratepayer Protection Act: any new load over 100 megawatts, which means an AI data centre, must pay the…
Which one is your own work built like: the data centre that can pause, or the factory that cannot?
Answer on LinkedIn →Quiz of the week
All weeksA one-minute power cut at a Samsung chip plant took how long to restart?
Ten questions from this week in AI and the factory floor. Two are match-ups. Every answer is a fact from a piece on this site or a public source, and every explanation says where it came from.
10 questions, 1 match-ups, about 4 minutes. Every answer links to the piece it came from.
Take the quizPick a door
The guided tour
15 piecesAI on the factory floor
What AI actually changes in a plant, and what it never will.
- 3 AI Power Moves, 1 Week, and a Rule Chip Factories Wrote in 2000
- AI Just Asked to Slow Down. Chip Makers Wrote the Rule in 1973.
10 pieces · 36 explainersMES & shop-floor systems
The software that actually runs a factory.
- OpenAI's Data Agent Reads 7 Databases. Not One Is on a Factory Floor
- 3 AI Agent Breakouts, 1 Week, and a Red Button From 1991
23 piecesSemiconductors: chips, fabs & yield
Why a chip you can design today still cannot be built for three years.
- SK hynix, Intel's Ohio Fab, and the Rule That Copies the Plumbing
- Everyone Is Announcing Capacity. Nobody Is Announcing The Number That Decides It.
One thing to try on Monday
All 42 tipsGive one weekly check a schedule and a hold rule, in ten minutes. Pick one check you do by hand every week, like reading three public pages and noting what changed. Open the Claude desktop app, click Scheduled in the left sidebar, then New task and Set up manually. Paste the check as the prompt with the three public page addresses, set the frequency to Weekly, and add one line at the end: "If a page will not open, say so and stop." Save it. It runs in the cloud on its schedule while your laptop sleeps, and you read the note on Monday. If your company gives you Microsoft 365 Copilot instead, the same lives under Automations. Public pages only, never company data. A chip factory does not wake an engineer at three in the morning to move a batch: the machine holds it and calls for help. Give your check the same deal.
Twenty years in the software that runs factories. One story a week on what it taught me.
Read about FabSpeak →One email. One story. Once a week.
The week’s breakdown, the one number behind it, the caveat nobody puts in the press release, and one AI trick you can actually use at work on Monday. No roundups. No sponsored sections.
You’re on the list. The first edition lands when it goes out; nothing before, nothing else.
- A correction. The most useful message you can send.
- You work in this layer and something here was wrong, or right for the wrong reason.
- Speaking, podcast or panel.
- Something you want explained. Recurring questions become episodes.