Where value goes when building is free 当"造东西"变免费,价值去了哪
AI is driving the cost of writing software toward zero. It's tempting to read that as "developers are finished." I read it the way an economist would: when the cost of one input collapses, value doesn't evaporate — it moves to whatever just became the new bottleneck. The interesting question isn't whether building gets cheap. It's what gets scarce when it does. AI 正把写软件的成本推向零。很容易把这读成"开发者完了"。我更愿意像经济学家那样读它:当一项投入的成本崩塌,价值不会蒸发——它迁移到那个刚刚变成新瓶颈的东西上。有意思的问题不是"造东西会不会变便宜",而是它变便宜之后,什么变稀缺。
When a cost goes to zero, value moves to the complements成本归零时,价值迁移到互补品
This is an old pattern. When one part of a system gets cheap, demand and value shift to the parts that are now the constraint. When building is abundant, the scarce things become: judgment — of everything that can be built, what actually should be, and for whom; verification — once generating an answer is free, knowing whether it's correct is the hard part; and the last mile — turning a capability into something that runs and is trusted in a specific, messy reality. "AI flattens the price of code" isn't the end of the story. It's value moving house — out of output, into judgment and verification. 这是个古老的规律。当系统的一部分变便宜,需求和价值就转移到如今成为约束的那些部分上。当"造东西"变得充裕,稀缺的东西变成:判断——在所有能造的东西里,什么才真该造、为谁造;验证——生成答案变免费之后,知道它对不对才是难的那部分;以及最后一公里——把一项能力,变成在具体、脏乱的现实里跑得通、被信任的东西。"AI 抹平代码的价格"不是故事的结尾,而是价值的一次搬家——从"产出",搬进"判断与验证"。
The thing AI structurally cannot do: be accountableAI 结构上做不到的那件事:被问责
There's one complement that matters more than the rest, and it's the one a model can't supply no matter how good it gets. A machine that moves — that can damage a part, or hurt a person — needs someone who can be held responsible for it: a name on the work, someone who carries the reputational and legal weight, who can be looked in the eye when it matters. A model cannot be accountable. It can't sign off, can't be liable, can't stand behind a decision when a regulator or an insurer or an injured person asks who is answerable. The more capable the automation, the more that accountable human layer is worth — not less. 有一个互补品比其余都重要,而且无论模型变多强都供不出来。一台会动的机器——会损坏工件、会伤到人——需要一个能为它被追责的人:作品上有名字、扛着声誉和法律的重量、要紧关头能被人看着眼睛。模型无法被问责。它不能签字负责、不能承担责任、不能在监管方、保险公司或受伤者追问"谁来负责"时站在决定背后。自动化越强,那个可问责的人的一层就越值钱——不是越不值。
Some ground commoditizes slower — on purpose有些地商品化得更慢——而且是必然
Not all software erodes at the same rate. In safety-critical and regulated work — anything where a mistake has physical or irreversible consequences — the very things that slow a project down elsewhere become the moat: liability, regulation, insurance, the hard requirement that a responsible person stand behind the system. That friction means the floor drops slowly, because "cheap and fast" was never the whole ask; "provably safe, and someone answerable" was. It's not a coincidence that the domains where verification and accountability dominate are the ones least threatened by abundant generation. 不是所有软件都以同样的速度被侵蚀。在安全关键和受监管的工作里——任何"出错会带来物理或不可逆后果"的地方——那些在别处拖慢项目的东西,恰恰成了护城河:责任、法规、保险、以及"必须有个负责的人站在系统背后"这条硬要求。这种摩擦意味着地板下降得很慢,因为"又便宜又快"从来不是全部诉求;"可证明地安全、且有人担责"才是。验证与问责主导的那些领域,恰是最不受"生成变充裕"威胁的领域——这不是巧合。
What this means for how I work这对我怎么做事意味着什么
I'm not betting that I write code better than a model — that's a bet you lose. I'm betting on the layer above the code: taking a powerful capability and being the accountable, trusted person who makes it safe to hand a consequential system to. That's why the way I work leans on the things that survive abundance — proof over claims, verification built in, bounded consequences, honest scope — and why I gravitate to problems where being right and being answerable matter more than being fast. When building is free, that's where the value went. 我不是在赌我比模型更会写代码——那是必输的赌。我赌的是代码之上的那一层:接过一项强大的能力,做那个可问责、被信任、能让人放心把有后果的系统交给他的人。这就是为什么我做事的方式,押在那些能在充裕中存活的东西上——证据高于声称、验证内建、后果有界、诚实定边界——也是为什么我被"对不对、谁担责比快不快更重要"的问题吸引。当"造东西"变免费,价值就去了那里。
← All notes← 全部笔记