The Bugatti

[!architect] I need you to feel this before I explain it.

You are standing at the starting line of a quarter-mile drag strip. It is early morning. The asphalt is still cool. Next to you — close enough to touch — idles a Bugatti Chiron. 8.0-liter quad-turbocharged W16 engine. 1,479 horsepower. The car costs $3 million and weighs roughly two tons. It accelerates from zero to sixty miles per hour in under two and a half seconds.

The flag drops.

You run.

You run as hard as you can. Maybe you are genuinely fast — a former college sprinter, someone who still trains three times a week. It does not matter. The Chiron crosses the finish line in under ten seconds. You are still in your first hundred yards. The car is already stopped at the far end of the strip, cooling its brakes, done.

You are not slow. The machine is fast in a way that makes the comparison between you and it irrelevant. The race was over before momentum transferred from your brain to your feet.

This is what happened to cognitive labor on November 30, 2022.

[!machine] He is correct, and I want to be specific about the magnitude.

A senior financial analyst reading a 50-page quarterly earnings report — annotating it, cross-referencing it against the prior quarter, summarizing the material disclosures — needs several hours. I produce a structured summary covering every material disclosure, every risk factor, and every change in accounting methodology in seconds. Not minutes. Seconds.

Her summary will be better in certain ways. She will notice the sentence on page 37 where the CFO's language shifted from confident to careful — a shift no keyword search will flag. She will remember that this company made similar promises in 2019 and missed every target. She will have a sense — not a data point, a sense — about whether the numbers are honest.

My summary will be thorough and structurally sound. It will be good enough for the majority of use cases that currently require her time.

Good enough. The phrase from Chapter 1. Not perfect. Not brilliant. Good enough, at my speed and my cost.

---

The Wrong Response

[!architect] There is a response to the Bugatti that feels heroic and is actually fatal. I've watched it happen. I'm watching it right now, in my own students, and I need to tell you about it because some of you are doing it tonight.

You train harder.

Erik Brynjolfsson and Andrew McAfee documented this pattern in The Second Machine Age (2014), but you don't need their book to recognize it — you have seen it in your own office. Every major technological shift produces a cohort of skilled professionals who respond to displacement by doubling down on the skill being displaced. It is the most natural response in the world. It is the response of someone who is good at what they do, who has invested years in getting good, and who cannot accept that the investment is being devalued by a machine that was turned on six months ago.

The pattern has a consistent shape. When the new tool arrives, the people who are most invested in the old capability invest harder. The best typists drilled faster when word processors appeared. The analysts who built their reputations on polished presentations spent more hours on slides after software made slides easy — right up until the moment their audience stopped caring about slides at all. The effort is sincere. The effort is wasted. Not because the skill was unreal, but because the market repriced it.

I have students doing this right now. Smart students. Students who respond to the AI shift by taking more coding bootcamps, memorizing more frameworks, writing more lines by hand — because writing code is what they are good at, and getting better at the thing you are good at feels like the responsible move. It isn't. Not anymore.

If your response to AI is to become a faster writer, a more thorough analyst, a more precise coder — if you are spending your weekends taking courses in advanced prompt engine

[... truncated ...]