The Chip So Big They Can't Throw the Broken Part Away

Every chip factory runs on one rule: cut the wafer into hundreds of chips, bin the broken ones. So what happens when your chip is the whole wafer? This week Cerebras reported cloud revenue up two hundred and eighty-one percent — on a processor the size of a dinner plate, fifty-six times a GPU. Nothing to dice. So what do you throw away? So how do you get yield on a chip you can't cut? You stop designing against defects and design for them: nine hundred thousand cores, each five-hundredths of a square millimetre. A defect kills one core; the fabric routes around it and the wafer keeps going. But here's what actually matters: wafer-scale let them skip H-B-M memory, CoWoS packaging and three-nanometre capacity — the three shortages everyone else is fighting. They didn't beat the bottleneck. They built something that never touches it. So where does your line still assume nothing breaks? Now, your FabSpeak Tip of the Week. This shipped on the thirteenth and almost nobody noticed: in Claude Code, your sessions can now talk to each other. Type the at sign, name a live session, and you message it directly. And subagents now fork by default — they inherit your whole conversation, so you stop re-explaining context, and they run in the background instead of blocking you. Still sitting there babysitting long jobs? Kick off the review in one session, keep working in another, message it when you need the answer. Then in slash config, set messages from your other sessions to hold. I checked the tooling in this build — the messaging is live and addresses sessions by name. That's FabSpeak. One story a week, taken apart properly.