The 100x engineer, and the unit nobody defines
- 5 minutes read - 938 wordsThe 100x engineer is back in the discourse. This time the pitch is that an engineer with the right AI tooling can do the work of a hundred. Sometimes the number is 10x, sometimes it is 100x, occasionally someone goes wild and writes 1000x. The number is always round and the unit is always missing.
What are we counting?
If a 100x engineer using Claude can do 365 days of work in 3.65 days, whose 365 days? A staff engineer shipping platform infrastructure? A junior wiring up CRUD endpoints? My grandmother on a good day? The denominator is doing all the work in that sentence and nobody ever writes it down.
The RPG item problem
There is a cleaner way to frame this. The “100x engineer” pitch sells AI tooling as a multiplier, the way RPG loot sells itself as *100 to all stats. The math of a multiplier compounds the floor: if your stats are 0.01, a *100 item brings you to 1. If your stats are 8, the same item flings you to 800. The marketing wants you to imagine the second case. The buyer is usually the first.
What AI tooling actually behaves like is a flat-add item. Roughly +0.99 to all stats. The kid at 0.01 puts it on and lands exactly at 1.00. The senior at 8 puts it on and lands at 8.99. Same buff, applied to whoever wears it.
Except a flat-add understates one thing: the senior extracts more from the same item. They know what to ask for, recognise when the output is wrong, slot the working bits into a system the kid does not have yet. The base buff is the same; what the wearer does with it scales with their level. Closer to +0.99 base, with a wielding bonus. Still not a multiplier on stats. The buff is on judgment, not on raw capability.
When someone tells me a terminal and Claude Code made them 100x, the question is not snark. What was the floor? If the AI item moved you from “could not ship a working CRUD app in a week” to “can ship one in an afternoon,” that is the +0.99 doing exactly what +0.99 does. Not a 100x engineer. A +0.99 wearer who started at 0.01.
The 100x story flatters more than “I was very junior and my tools got better.” Same story. Tells you nothing about the ceiling, only about the floor the speaker was sitting on.
A multiplier without a base is a vibe, not a measurement.
A concrete counter-example
Tunes is the music app and backend I have been building on weekends, a Go service plus SwiftUI clients on iOS, macOS, and tvOS, replacing iTunes Match for my own library. AI has been in the loop on almost every commit. I am close to a year of weekend development and the thing is not shipped.
If 100x were real, Tunes should have been done sometime around last February. It was not. The reason is not that I was idle. Building a real product is mostly the parts AI does not compress: deciding the data model, debugging a SwiftUI animation that only misbehaves on tvOS, understanding why the Go service drops connections on a specific HLS edge case, designing the play queue semantics, redesigning them after I lived with the first version for a month.
The model writes the function. I still have to know which function to ask for. Otherwise I get a bubble sort hidden inside a request handler that takes 45 seconds for no good reason, and the model will defend it with a straight face until I push back.
AI maggots will read this and tell me it is a SKILL.md issue, that the model would have known better with the right rules file pinned to the context. Sure. It is a skill issue. Just not the kind they mean. The wielding bonus shows up here.
The token economics nobody is pricing in
The unit cost of all this is currently subsidised. Frontier model access is sold below what it costs to serve, on top of training spend that has not been amortised. Investors are paying so we get to play with cheap intelligence. That ends. It always ends.
When the price of a token starts to reflect what a token actually costs, the productivity story gets re-litigated against a less generous backdrop. The engineer who burned three thousand tokens flailing at the bubble sort and the engineer who spotted it in twenty seconds are doing very different work. Today they pay roughly the same. Tomorrow they will not. The boring metrics will show up: cost per shipped feature, cost per resolved bug, cost per regression caught before production. Management likes impressive marketing metrics. Field reality is usually a bit different.
The engineer in that scenario is in the same position as the buyer of a smart speaker whose vendor pivots, or the company shipping on top of an open source project that changes direction. Different floor, same shape: you built on something you do not own. The buyer floor and the vendor floor live in other posts. The engineer floor is here.
Real gain, yes. Not 100x, not 10x averaged across a real week. A +0.99 with a wielding bonus, applied to whoever wears the item. Sentence does not get retweeted, which is why it does not get shipped.
Anyone using the 100x number is selling something or measuring something silly. If they are selling, ask what the unit is and watch them squirm. If they are measuring, ask them to print the denominator on the next slide.