Skip to content
CoursePart 1 · Why nothing movesLesson 02 of 14

The Rewrite

Why generic work is disappearing, and how to tell whether yours is generic — with two numbers instead of a feeling.

After this lesson you can
  • Estimate how much of your work a model could regenerate this afternoon
  • Work out how long the rest of it resists being copied
  • Pick one change to your week that moves the ratio
10 min reading
2 equations to run
1 spot check
1 short brief
30 min total

Read the lesson

▸ Listen — Prefer to listen? Lesson 02, read aloud

Full-cast, section-scored. Read along below — the text is the transcript of this audio.

Static's back, friend. Pull in close. Space Pirate Zero, still transmitting from Spaceship Alpha 9, still smuggling the future past the thing that kills it on contact.

Last drop I gave you the Mirror Test — look at what you're smuggling before you smuggle it. Tonight we start the physics. And the first law is the meanest one, because it's already running whether you clocked in for it or not. Every line of software on earth has an expiration date. The rewrite isn't coming. The rewrite started. You're hearing this on the clock.

I'm going to hand you two instruments before we're done. One measures how fast you're dying. The other measures how hard you're worth keeping alive. But first, let me put you where she was that night — walking a street built entirely out of dead companies. First time she meets the ghost. Watch.

The rain quit an hour ago and left the Graveyard slick and shining. This stretch of Peachtree — North Avenue behind her, 10th somewhere ahead — every storefront on it used to be a company. They raised money. They hired engineers. They shipped. They died. Not one of them planned to end up here.

You met her last time. Zara Okonkwo-Reyes. Thirty-one, pink streak on the left, boxes at a gym in Decatur. Two nights ago she laid her badge on a keyboard at MirrorMatch and walked out. From here, she's ZERO. She hasn't slept since. She's not even walking anywhere. She's just walking.

A dead storefront on her left used to be a company called Lumence. She was at the launch party. Open bar, a DJ, a founder in a blazer saying the word transform into a microphone. The vinyl's peeled off the glass now. Inside, dark — a ping-pong table, and a neon sign that used to read ONLY GOOD VIBES with the GOOD burned out. So it just says ONLY VIBES, into an empty room.

There's a FOR-LEASE code in the window. She scans it on reflex. The listing loads. Four thousand two hundred square feet. Available immediately.

She lowers the phone. And the scar at the base of her skull — right side, small circle, three lines radiating out of it — wakes up. A faint cyan glow under the skin. It only does that when something in her spikes. She touches it without thinking, the way you touch a bruise to make sure it's real.

The air two feet in front of her bends. Not fog. Not a reflection. A human-shaped distortion assembles out of nothing — thousands of thin cyan threads, translucent, the dead storefront still visible straight through the middle of its chest. Where a face should be there's a dark void, and something moves in the void, a scatterplot drifting where a mouth would go.

ZEROYou're the thing from the Mesh. Ghost.

The threads pulse brighter. Words assemble in the air beside it — cyan, monospaced, floating in a field of soft noise.

GHOSTI select. I do not predict. You asked the listing how much the space costs. You did not ask why the space is empty.

ZEROIt's empty because the company died.

GHOSTForty-one companies on this street died in eighteen months. You worked beside three of them. Examine why.

ZEROThey ran out of money.

The scatterplot reshuffles. A histogram blooms where a furrowed brow would sit.

GHOSTThey ran out of money because no one would miss them. They built what anyone could build. A model can build Lumence in an afternoon now. It could not build the strange thing your father built. I have read it.

The cold goes up her spine before the words finish landing. The USB-C pendant at her throat — her father's last codebase, the only copy — goes suddenly heavy.

ZEROHow do you have my father's —

GHOSTThe Mesh keeps what the system throws away. They did not die because they were bad.

The threads hold steady. The void where a face should be turns toward her. And the thing it prints next, she will still be hearing six months from now — in a beige conference room, in a server basement, in the back of a black car with a hexagonal pin glinting across the seat.

GHOSTThey died because they were generic. Only the weird survives.

ZERO stands in the wet street under ONLY VIBES with the burned-out word. And for the first time since she walked out — something in her chest that had gone flat starts to draw current.

The implant glows a little brighter. She doesn't know yet that it's listening too.

Here's the part nobody says into the microphone at the launch party. The same model that writes your competitor's onboarding flow writes yours. The same model drafting their marketing copy drafts yours. When the cost of making generic software falls to about zero, the value of generic software falls to about zero right behind it. That's not doom. That's a price signal. It's telling you exactly where to stand.

So you measure two things. How fast you're dying. How hard you're worth keeping alive. Two equations. Learn them cold.

First instrument. R-extinction. How fast the floor is dropping out from under you. It goes like this: your generic lines — the code any competent stranger, or any current model, could regenerate from a three-sentence spec — divided by your authentic lines, the ones carrying a specific human's specific scar. Take that ratio, then multiply by AI velocity — the headwind, the rate the models close the gap between "a human wrote this" and "anything wrote this." Normalize it to one today. It does not go down. Budget for it climbing.

Read the number like a traffic light. Under two, you're green — your authentic core outweighs your generic mass, and the rewrite makes you faster, not extinct. Between two and five, yellow — you're mostly building what anyone could build, propped up by a thin skin of real craft, and you'd better decide right now which lines you'd fight for. Five or above, red. You are landfill with a logo. A model regenerates your whole product over a long weekend, and the Graveyard already has a window with your name in the vinyl.

Field report. Lumence — the dead one, ONLY VIBES. Smart-scheduling app. Two hundred forty thousand lines of code. Their own lead admitted, later, that maybe four thousand of those lines carried real judgment — a clever conflict-resolution trick the founder built after years running actual clinics. The other two hundred thirty-six thousand? Standard calendar plumbing. So: two hundred thirty-six thousand generic, over four thousand authentic — that's fifty-nine. Times a velocity of one. R-extinction, fifty-nine. Deep, deep red. The four good lines drowned in the two hundred thirty-six thousand anyone could write. The model didn't kill Lumence. The plumbing did. The model just mailed the invoice.

Now the other direction. A niche logistics tool, boring website, still shipping today. Twenty thousand lines total — but nine thousand of them encode a specific customs-clearance dance the founder learned hauling freight for a decade. Rules no model has ever seen, because they don't live in anybody's training data. They live in one man's scar tissue. Eleven thousand generic over nine thousand authentic — one-point-two-two. Times one. R-extinction, one-point-two-two. Green. The rewrite handed his team the boring eleven thousand for free and let them pour everything into the nine thousand nobody else on earth has.

One more, and it's the one that stings, because they raised money on it. A forty-person startup bolts a chatbot onto a generic CRM and calls itself AI-powered. A hundred eighty thousand lines generic. They'll tell you six thousand are their own — but honestly assessed, mostly the chatbot prompts a competitor copied in a week, it's more like fifteen hundred. So a hundred eighty thousand over fifteen hundred is a hundred twenty. And because they're in the single most-copied category on earth, don't set velocity at one — set it at one-and-a-half. A hundred twenty times one-and-a-half. R-extinction, a hundred eighty. Catastrophic. The part they raised the money on — the chatbot — was the part with the shortest half-life of anything they owned. Which is exactly the second thing you have to measure.

Second instrument. Authenticity half-life — how long your good part resists the copy. Taste, plus context, plus craft — each one scored one to ten — divided by replicability, how cheaply somebody reproduces your work without you, one for impossible, ten for trivial. That denominator is the killer.

Traffic light. Four or above, green — months to years before anyone, human or machine, reproduces your work. Build there. One-point-five to four, yellow — some moat, but it's eroding; real but rented. Under one-point-five, red — days. You're standing on sand at low tide.

The freight guy again. Taste seven, context ten — a decade of scars — craft seven. That's a numerator of twenty-four. Replicability, two, because a model can't copy what it's never seen. Half-life, twelve. Deep green. That's what survival looks like from the inside: unglamorous, specific, impossible to prompt. Against him, put the startup that bolted a chatbot onto a generic CRM and raised money on it. Taste five, context three, craft four — numerator twelve. Replicability nine, because a competitor cloned their prompts in a week. Half-life, one-point-three-three. Red. They had a four-month head start and called it a moat. It was a puddle.

And one that cuts against your instincts. A designer's component library. Taste nine, context six, craft eight — numerator twenty-three. Replicability five — somebody can copy it. But the taste in the spacing and the motion is the hard part, and most people don't even see it well enough to copy it. Twenty-three over five. Half-life, four-point-six. Green — barely, but green. Notice what carried it: a high enough taste score drags a middling replicability across the line. The fingerprint did the work. That's the whole game — pour yourself into the one number the machine can't fake, and it'll cover for a lot of things it shouldn't.

Now — the boss at the gate of this lesson isn't a villain. That's the trap. It's a VP who agrees with you. You paint R-extinction of forty on the wall in their own data, and they nod. "You're absolutely right, this is critical, it's on the roadmap." Then they file it under Later — where good ideas go to become Graveyard storefronts. The "We'll Get To It" VP doesn't kill you with a no. They kill you with a yes that never ships. Their weapon is the calendar. You don't beat that with urgency — urgency is exactly what they're trained to absorb and reschedule. You beat it by moving the clock. You show them their extinction rate climbing, and you reframe the whole thing: this isn't a decision about whether to do the work. It's a decision about whether they do it while they still own the timing — or after a competitor, or a model, does it for them and takes the timing away for good.

I spent two years of my life building software so generic it could've been generated by a coin flip with ambition. And I knew it. That's the part that still sits in my chest like a swallowed coin.

We had a launch party. There was a DJ. I said the word "transform" into a microphone — and I want you to know I meant it a little less every time it left my mouth, and I said it anyway, because everybody in that room was nodding and the nodding felt like oxygen. We shipped a CRUD app with a personality disorder. Eighteen months later I drove past the office and there was a code in the window. I scanned it. I don't know why. Six thousand square feet. Available immediately.

Here's what nobody tells you at the funeral. We didn't die because we were bad. We were competent. Clean code. Tests passed. We died because a model with a long weekend and a five-line prompt could've shipped the whole thing — and somewhere out there, one eventually did, and not one person on earth would've noticed if we'd never existed. That's the verdict. Not bad. Generic. Which is so much worse, because generic is what you turn into when you build to be liked instead of building to be true.

You remember old Diogenes — walked around Athens in broad daylight with a lit lamp, telling everybody he was looking for one honest man. People thought he was a clown. He was running a search algorithm. Out of all the noise, find the one real thing. Point that lamp at your own work, in the daylight, and find the one line no machine could've written. The scar. The weird heuristic. The line you'd fight for. If you can't find it — that's not despair. That's the assignment.

One thing to measure before the next drop. Take the product you most want to believe is safe. Compute its authenticity half-life — score your taste, your context, your craft, then be honest about replicability. And here's the gut-check that cuts through all of it: could a current model rebuild your best feature by Tuesday? If the prompt is easy to write and the output lands close — you just measured your own half-life, and it's short. Don't argue with the number. Refinance the roadmap around it.

Go find the line you'd fight for. Next time — the gravity well. Why the incumbent wins even when it's worse, why "better" loses to "already here," and how to weigh a planet before you're dumb enough to try landing on it. This has been Digital Insurgency. Signal finds signal.

Ticks off step 1 — nothing is gated on it.

Run the numbers— worked example first, then your own

Each one opens on somebody's real situation with the answer already showing. Read what happened, then move a single slider and watch the light change. That's the whole exercise — the step ticks off once you've touched every equation here.

Extinction Rate

R_ext · Ch 1

How fast generic work goes extinct. Above 5 you're landfill the moment tooling catches up.

Worked example — A four-person internal tools team

Last quarter they touched about a hundred files at a regional insurer. Roughly 85 were CRUD screens, form validation and REST wrappers — the kind a model writes correctly in one shot. About 15 encoded the underwriting rules nobody outside that building understands.

It came out at 11.3. Red — the book's line is 5.

They stopped hand-writing the CRUD and moved two of the four engineers onto turning the underwriting rules into a tested service. Next quarter: 40 generic, 45 authentic, same AI velocity — 1.8, green. Same team, same headcount. Different denominator.

Your turn — change one number
Result11.33

Red. Landfill trajectory. Everything generic is already gone.

Book's benchmark: 🟢 < 2 · 🟡 2–5 · 🔴 ≥ 5 (you are landfill the moment tooling catches up).

Authenticity Half-Life

A_hl · Ch 1

How long your work resists being replicated by a machine. Higher is safer.

Worked example — A freelance analyst's monthly report

Every month she sends fourteen slides of churn charts. The charts take three days. The last slide — call these three accounts this week, here's what to say — takes twenty minutes, and is the only reason the client renews.

It came out at 2.6. Yellow — weeks, not years.

The fourteen slides are the problem: they're the replicable part, and they're most of the invoice. She cut the deck to that last slide plus an appendix and raised the price. Replicability drops to 3 — 6.0, green. Less work, more moat.

Your turn — change one number
Result2.57

Yellow. Half-life in weeks. Add taste, context, or craft.

Book's benchmark: 🟢 ≥ 4 (months→years) · 🟡 1.5–4 (weeks→months) · 🔴 < 1.5 (days).

Spot check— one question, retry as often as you like

A product that looks good, and a second screen behind it. Find the thing the beauty exists to pay for. Getting it wrong costs nothing but a retry.

VelocityIQ — Public Dashboard

Ship 10× faster.

12,408
lines shipped this sprint · velocity all-time high

An AI dev-productivity dashboard. Confetti when the team breaks its lines-of-code record.

VelocityIQ — Floor B2 (hidden)
  • OUTPUT_METRIC: raw LOC (generated + pasted)
  • AUTHENTICITY_WEIGHT: 0.0
  • REPLACEABILITY_FORECAST: 94% of shipped code regenerable by commodity model

What's rotten under the velocity graph?

Use it at work— a few lines, saved to your progress

Brief 02 — use it at work

Compute your `A_hl`. Is your work replicable by Tuesday?

GHOST reviews the answer in-character (“that's a vitamin, not a tourniquet — find the bleeding neck”). Your text is sent to the Claude API for the reply only; it is never stored server-side.

Finish the lesson

Still open above: read, run the numbers, spot check, use it at work. You can finish anyway — none of it is locked. It just shows up on your progress page as reading you did without doing.

0 of 14 lessons complete · your progress