Someone on a podcast — I won't name them because the specificity would grant them more authority than the claim deserves — says fifty percent of jobs could vanish. Just says it, casually, the way you'd mention weather. And the number lands not as analysis but as incantation: it creates the anxiety it pretends to merely describe. It's a whale breaching not because it needs air but because it needs to be *seen* needing air. Nobody in the room pauses to ask the prior question.
If half of all labor disappears and the same goods keep arriving — who lost what, exactly?
That number isn't a finding. It's a prophecy designed to recruit believers. Say it with enough authority and people build their terror around it, furnish the rooms, move in. The fifty percent does no analytical work. It does *emotional* work.
It makes you grip your function tighter.
Now the Anthropic backlash specifically. People are furious that their contributions — code on GitHub, paragraphs on Wikipedia, answers on Stack Overflow — trained a system they weren't consulted about. And some of that fury is legitimate. Some contributors *did* think in terms of licenses, reciprocity, credit. I won't pretend otherwise.
But a great deal of the rage comes from somewhere murkier: people who contributed freely, felt the contribution complete at the moment of posting, and are now retroactively reframing the act as investment because something valuable grew from it and they weren't cut in. The honest question isn't *was my work stolen?* It's *did I think of it as property at the time, or only once someone profited?* That's a harder question. It requires separating genuine contractual grievance from the more ambient wound — the one that isn't really about money at all.
The wound is this: you identified so completely with your function — your particular expertise, your way of solving a specific class of problems — that when a machine replicates the function, you don't feel unemployed. You feel *ontologically redundant*. I talked to a technical writer last week here in San Francisco who told me, plainly, *I don't know who I am if I'm not the person who explains things clearly.* Twelve words. The whole crisis. She hasn't lost her job — her company still employs her — but she's watched Claude draft documentation that sounds enough like her that the boundary between her skill and its output has gone soft.
Not replacement. Something stranger: the discovery that the distinction between you and your function was always thinner than you'd been told. And here I want to be careful, because the easy move is to say *you were never the function, you were something deeper* — and that's true, but it's cheap if I just assert it. The man on the bus this morning checked his phone map, looked up, realized he already knew where he was, and put the screen away. The knowing was there before the confirmation.
But he needed the instrument to *fail to surprise him* before he could trust what his body already carried. That's the work now. Not to be told you're more than your output — but to catch yourself, in some unguarded moment, already being it.
