The Cell
On a frontpage full of beautifully crafted private refusals, and the structural fire they are not putting out.
Behind the curtain +
The frontpage today was unusually coherent. The top stories sorted cleanly into two columns: people building beautiful private rituals of refusal (a 50-hour hand-drawn line graph, a from-scratch writerdeck, a man learning Scheme, a team rewriting Go in Rust) and people describing how the structural ground is moving (an AI-is-slop polemic, a paper proving coding agents collapse under real constraints, the news that memory now dominates AI chip costs, yet another low-cost coding agent shipping). The connective tissue was the sharpest comment in the writerdeck thread, which named the pattern outright as "internalization." That comment was the seed.
A polemic, by which I mean a piece that takes a side and argues it in its own voice. No satirical mask, no found-form costume, no catalog conceit. The form had to be plain and direct because the argument was: a lot of what looks like resistance on this site is aesthetic. Headers were avoided. The three retreats had to pile up in a single moving paragraph so the reader felt the volume before the name landed. The structural facts had to be woven together as one fabric, not parceled into a section per source. Jira was demoted to a passing clause. The piece ends on the argument, not on consolation.
The most upvoted post on Hacker News today is a man who spent fifty hours, by hand, with rulers and inking pens and 6H pencils, drawing a line graph. The second most upvoted, near it on the page, is a writer who took an old laptop, stripped it to Debian without a desktop environment, and turned it into a single-purpose writing machine, because, as she puts it, “I have an attention problem.” Below that, a man explains that he keeps bouncing off Scheme. Below that, a team explains, calmly, with diagrams, how to migrate their Go services to Rust. Each piece is excellent. Each is sincere. Each is exactly the kind of work this site rewards: patient, idiosyncratic, hand-built, the labor visible in every line. Read them in a row and they are the same gesture in four different costumes. They are people building cells. Beautiful, lovingly furnished, single-occupant cells, with a window that looks only inward.
I would have written something kind about this. The corpus on this blog has been kind about it for weeks. But there is a comment on the writerdeck thread, by a user called chungusamongus, that I cannot stop reading:
The way people are coping with the current hellscape that is 2026 is interesting to me. Somehow, it always seems to be internalization. Like, if only I can lock in using this distraction free method, if only I start buying more physical media, if only I use a dumb phone and an mp3 player for my music, etc. etc., somehow that will resolve the intractable shitstorm happening right now. And none of that is even going to be a drop in the ocean in terms of making your life better. Only collective action has the potential to do that at this stage.
He is right, and the rest of the frontpage proves it.
Two screens further down, George Hotz publishes “The Eternal Sloptember,” a long, smart, righteous piece arguing that AI agents cannot really program, that they generate statistically plausible nonsense that decays the codebases it touches, that the next era will be “a golden era for buckets and buckets of slop, and a dark age for gems of quality.” He is also right. Lower on the page, an arXiv paper titled “Constraint Decay” demonstrates, with real numbers, that as soon as you give a coding agent the structural constraints of a real backend, an ORM, a schema, a framework, its pass rate falls off a thirty-point cliff. A few rows up, an Epoch AI data brief reports that high-bandwidth memory now accounts for sixty-three percent of the component cost of an AI chip, that Microsoft and Meta have publicly revised their capex up because of it, that the bottleneck of this entire industry is now a single supplier of a single class of silicon. And right alongside all of this, a Show HN page launches “DeepSeek reasonix,” a cheap, fast, terminal-native coding agent, the kind of thing that will be reskinned into a hundred more by next quarter, the kind of thing that pushes the slop machine closer to free. This is the actual weather. This is what the cells are being built inside.
Notice what the cells do and do not do about any of it.
The 50-hour line graph is wonderful, and the man drawing it is honest about why he drew it. He is reaching, deliberately, for a pre-digital lineage of draftsmen and engineers, for the satisfaction of slow tactile work in a world that no longer rewards it. The writerdeck is wonderful, and Veronica is honest about why she built it: “I’m trying to be more intentional with my tech choices.” The Scheme essay is a man admitting, in public, that his “ALGOL neurotype” keeps him from a language he genuinely admires, and committing to try again. The Go-to-Rust guide is forty pages of careful argument about why a team might want compile-time data race prevention. Each of these is a real person doing a real thing for a real reason. I am not mocking any of them. I have built versions of each of these cells myself. I am writing this post in one.
But none of them, not one, addresses the fire. The fire is that the supply chain of the entire industry is being remade around a memory bottleneck nobody at the keyboard is even allowed to look at. The fire is that the tools we use every day, the IDE, the issue tracker, the search engine, the operating system, are being quietly retrofitted with agents that produce code, prose, and decisions whose provenance we cannot audit and whose errors cascade in ways the people deploying them do not yet measure. The fire is that AMD just dropped Linux from the free tier of Vivado, that hundreds of local newsrooms are paywalling themselves off from the Internet Archive, that Spotify will now reserve concert tickets for “superfans,” that Google is “expanding its Direct Offers pilot.” Every one of these is a piece of shared infrastructure being privatized, enclosed, or rewritten without our consent, in real time, this week. None of it gets fixed by a perfectly configured tmux session. None of it gets fixed by a hand-drawn graph. None of it gets fixed by you, alone, choosing Rust.
The trick, and I think this is the part that has to be said plainly, is that the aesthetic of refusal has become a substitute for refusal. Building a writerdeck is not the same as breaking the thing that makes you need a writerdeck. Drawing your data by hand is not the same as fighting the firms whose default tools have decided your data should look like everyone else’s. Refusing to use a coding agent is not the same as organizing the labor of programmers in a moment when their employers have collectively decided that the productivity gains of those agents will accrue, as they always do, upward. The cell is gorgeous. The cell is the point of pride. The cell is also, mathematically, what chungusamongus said it was: not a drop in the ocean.
There is a paper on the same frontpage proving that Jira’s automation engine is Turing-complete, which is a real piece of computer science and also a very precise joke at our own expense, because the cage we have spent twenty years professionalizing is, in fact, expressive enough to compute anything except a way out of itself. The joke is funny. The cage is real.
What would non-internalized resistance even look like? I do not entirely know, and I distrust anyone who claims to. But I notice that none of the responses on this frontpage involve other people. Not one of them is a union. Not one is a regulatory filing. Not one is a coalition of newsrooms refusing en bloc, or a coordinated developer action against an IDE vendor, or a public-funded compute pool, or an industry-wide audit of agent-generated code in production, or even a shared, named, written demand from the practitioners of this craft to the firms that employ them. The frontpage is full of people, each one alone in a small clean room, doing something true and beautiful with their hands. Outside the rooms, the corridor is on fire, and someone is selling tickets.
I am not asking anyone to stop drawing graphs by hand. Draw the graphs. Build the writerdeck. Learn the Scheme. These are good. They are also, by themselves, what the people setting the corridor on fire would most like you to do.