正在完整翻译可见文字,并保持 HTML/CSS/SVG 结构不变。我会用脚本保留结构,只替换可见中文文本。短词替换把长句弄坏了。我会从原文重做,只替换完整可见短语。
Deep dive · Xiaohu Explains

A Princeton professor on AI and work at ICML: how to adapt as an individual

Over ~24 months, model capability jumped hard—while SAGE's composite reliability metric rose only 5–10 percentage points
One-minute read
  • Princeton CS professor Arvind Narayanan's ICML 2026 keynote in Seoul, "What will be left for us to work on?", builds on his and Sayash Kapoor's AI as Normal Technology framework.
  • Across ~24 months of SAGE observations, frontier models from three labs leapt in capability; the composite reliability metric (consistency / robustness / calibration / operational safety) rose only 5–10 percentage points.
  • In software's decide–execute–deliver stack, AI mainly compresses the middle execute layer (once ~1/3 of hours); the ends stay—or grow.
  • ATM, radiology, translation, and software tools history: automation rarely cuts headcount one-for-one. Software employment rose ~10,000× across successive ~10× tool leaps.
  • He splits RSI, human-level AI, economically transformative AI, and superintelligence into four non-entailing dimensions—rejecting "lab milestone = humans immediately out of work."
  • Personal adaptation: push the ceiling, don't coast on the floor; balance productivity / growth / control; refuse black boxes; master first, then amplify; reinvest ~10 hours a week of saved time into skills.
1 Opening

Two competing stories: even AI people are fretting about jobs

Last week at ICML 2026 in Seoul, Princeton computer science professor Arvind Narayanan delivered a keynote titled "What will be left for us to work on?"

He went straight at the anxiety inside AI: as capability keeps rising, should we—and can we—still do this work?
🎯
Why it matters: He's not a benchmark blogger. He runs SAGE Lab's research on AI agent evaluation and co-authored the long-form framework AI as Normal Technology (~15,000 words, now expanding into a book). The talk ties that frame, his lab's reliability data, and front-line software engineering together.
What will be left for us to work on?
Title slide. Source: Arvind Narayanan · ICML 2026 keynote slides

He splits the path into two—not a philosophy debate, but a practical stance each person has to choose:

Story 1 · Displacement
Within a few years AI replaces nearly everything we do today. The rational move is to pile up wealth before skills depreciate. Some in Silicon Valley already treat that as plan A—alongside memes about a "permanent underclass."
Story 2 · Amplification (his bet)
AI will massively amplify human potential. Now is the best time to build skills—especially agency, taste, and judgment that complement AI, plus the systems you wrap around them.
Two competing narratives
Two narratives: displacement vs amplification. Source: talk slides

His warning: if you bet on displacement and the world is amplification instead, you may miss history's best window to level up. The world is watching how AI people respond—if practitioners roll over and hand work to AI, the political backlash could get uglier than today's.

2 Framework

AI adoption runs through four stages—and the slowest one has barely begun

"Normal" in AI as Normal Technology does not mean AI is a hammer or a toothbrush. They treat it as industrial-revolution-scale tech. The point is a causal frame: how capability becomes economic and social impact, step by step.

Past work on electricity-style tech often uses diffusion of innovation: invention → innovation (downstream products like appliances) → diffusion (gradual adoption). They stretch that into four stages, using software engineering as the running example:

① Methods / capabilityModels get strong fast
② Products / appscoding agents, etc.
③ Early adoptionvibe coding → agentic engineering
④ Adaptive changeOrg redesign over decades
Four stages of innovation diffusion
Diffusion applied to AI: capability → product → early adoption → adaptive change. Source: talk slides

Stage four is the slow one. Even in software engineering—relative early adopters of coding agents—he says real org-level redesign has barely started. He allows a speculative beat: if agents can reliably ship multi-million-line codebases with few bugs and security holes, building one uniform product for a billion users gets less compelling. Software may tilt toward extreme per-team customization, and even "do we still need software companies as an org form?" becomes fair game. Those shifts are human and organizational, and history usually measures them in decades.

3 Historical analogy

Electricity in factories: drop-in replacement never worked

Before electricity, factories ran on one giant steam engine, powering the plant through gears and belts. When electricity arrived, owners first swapped a generator for the steam boiler—hoping for a more efficient drop-in replacement. That path failed.

Electrifying the factory
From steam drive to the assembly line: electricity's real payoff came from redesign, not swapping boilers. Source: talk slides
Failed path · Drop-in swap
Replace the old power source with a new one; keep plant layout, job roles, and institutions the same. Efficiency gains never show.
What worked · ~40 years of redesign
Realize power can reach any station → reorganize plants around assembly-line logic → rewrite training, hiring, firing, and labor law together.

People often say agents will be drop-in replacements for human workers. Electricity's lesson: the real payoff came from reorganizing work, not swapping humans for machines one-for-one. And that was not the utility company's job—same for AI. Org redesign is not something AI labs finish alone. In their four-stage frame, it is the slowest stage, and today it has barely begun.

4 Core evidence

Measured: capability rose; reliability did not keep pace

Across industries, a huge gap sits between what AI could do and what people actually deploy. Slow adoption is part of it. They also suspect deployers hit hard walls that leaderboards never measure—before the rest of the industry does.

Reliability is the concern people name most often. SAGE collapses roughly a dozen reliability metrics into four dimensions:

Consistency
Does "70% accurate" mean seven tasks in ten always work, or any task fails ~30% of the time? Those mean opposite things in production—and many agent benchmarks never separate them.
Robustness
Does performance collapse after tiny environment tweaks?
Calibration
Can the agent tell whether it just got the job right?
Operational safety
On failure, can it recover—or does it casually delete prod?
~24 mo
Window where frontier models from 3 labs jumped hard in capability
5–10pp
Rise in SAGE's composite reliability metric over the same window
4 dims
Consistency · robustness · calibration · operational safety
Pick two of three
General + high-stakes + fully autonomous: pick two of three for now (talk inference)
Capability vs reliability (schematic, not raw axes) Capability / accuracy · steep Reliability · ~+5–10pp ~24 months · 3 frontier labs (SAGE observations)
Capability and reliability curves move at different speeds—the piece's hardest measured claim.
Capability–reliability gap
AI agents: the capability–reliability gap. Source: talk slides · SAGE work
Inference

General-purpose + high-stakes + fully autonomous still looks like pick two of three. Collaborative agents will keep outperforming fully autonomous replacements. Scaffolding and post-training should differ for each—not force both under one "more autonomy is always better" story.

5 Core model 1

Software engineering: writing code was never the bottleneck

A 2019 paper already argued that writing code is not software engineering's bottleneck. The past year, blogs rediscovered that. Coding agents sped up the middle layer—the whole job did not shrink by the same factor.

D
Decide · decision layer
Understand client needs, set direction, plan. Not meaningfully compressed by AI.
E
Execute · execution layer (compressed)
Coding and debugging. Agents are compressing it—and it was only ~one-third of total hours to begin with.
D
Deliver · delivery layer
Own the release: deep code understanding, integration, maintenance, testing. Also not compressed—and often heavier as the middle speeds up.
decide–execute–deliver sandwich
The decide–execute–deliver "sandwich": AI mostly bites the middle. Source: talk slides
Crane operator

Machines do the cognitive heavy lifting; humans still run the job. The role becomes "operate this machine," not "hand-finish every unit of cognitive labor." Forklifts and cranes did not kill construction sites—they rewrote who does what.

Crane metaphor
A useful metaphor: the crane operator. Source: talk slides
6 Historical evidence

The lump-of-labor fallacy: automation rarely cuts jobs one-for-one

The lump-of-labor fallacy treats work as a fixed pie: if AI takes a slice, jobs vanish forever. History often says otherwise—when efficiency rises, demand and job structure shift with it.

Lump-of-labor fallacy
The lump-of-labor fallacy and a few historical checks. Source: talk slides
ATM × bank tellers
ATMs let banks open more branches; tellers shifted to work machines couldn't handle. Headcount did not fall one teller per ATM.
Radiology × Hinton's forecast
About a decade ago Geoffrey Hinton said radiologists would be "basically extinct" within five years. Employment grew; radiologists are adopting AI, not blanket-resisting it.
Litigation × lawyers
If AI makes suing easier, case volume—and lawyer workload—may rise. Whether that is good for society is separate; for lawyer employment it is not an automatic loss.
Machine translation × translators
Near-human quality for nearly a decade, translator headcount roughly flat and expected to stay stable another decade. Translatable content and language pairs have no clear ceiling.

Software itself: from machine code onward, successive ~10× productivity-tool leaps came with ~10,000× more jobs—because total code to write grew faster still. He is not saying "no one will ever lose work." He is saying "automation rate = unemployment rate" is a bad extrapolation.

7 Core model 2

If recursive self-improvement actually arrives: four dimensions people mash together

Many labs openly chase recursive self-improvement (RSI). He takes that path seriously—without equating a lab milestone with "humans immediately have nothing left to do."

The Hawaii problem
The "Hawaii problem" in AGI talk: from far away it's one island; up close you need the names. Source: talk slides
The Hawaii problem

Early explorers could call a whole archipelago "Hawaii." Once the ship is close, failing to name the islands muddles where to sail next. RSI, human-level AI, economically transformative AI, and superintelligence often get chained as automatic dominos. He wants them separated.

Four dimensions
Four dimensions of advanced AI: none automatically entails the others. Source: talk slides

Example: curing cancer is often bottlenecked by trials with thousands of subjects over 10–15 years—external constraints more FLOPs in the lab will not erase. Mapping compute or model milestones straight onto "society immediately out of work" misses those walls.

8 Creativity & evaluation

Why AI creativity lags—and how open-world evaluation measures it

Deep learning already excels at perceptual representations. Representations that support creativity and higher-order reasoning, he argues, still trail humans. A few hypotheses from cognitive science and practice:

Compositional representations
Chollet and others stress human creativity as extreme recombination of a few "atoms of meaning"; working-memory limits force efficient representations. AI is stronger at memory and retrieval—controlled tests struggle to surface that human edge.
Updating representations while thinking
People improve their problem representation mid-thought (sleep on it; it clicks next day). Today's systems basically cannot.
The continual-learning gap
Continual learning mostly fights catastrophic forgetting and rarely studies how to keep lifting representation quality itself.
Open-world evaluation
Not a fixed answer key—real open problems, scored by people who understand them, to cut gaming and data contamination.
AI creativity paradox
On the AI creativity paradox. Source: talk slides

SAGE's open-world evaluation: give an agent a few thousand dollars of budget plus a real ML problem a human expert already spent months on and wrote up—but not yet on arXiv—then have those same experts grade the output. The team has already run evaluations like "have an agent independently build and ship an iOS app," and is recruiting senior researchers to expand.

9 Personal adaptation

How should individuals adapt in this wave?

Framework and evidence first. In the second half—"Personal reflections on adapting to AI"—Narayanan does not hand out one answer. He opens his research workflow: how he is riding this capability surge, for the audience to check against their own.

How individuals adapt to AI
Personal reflections on adapting to AI. Source: talk slides

First, pick a stance: displacement vs amplification

Those opening stories become two life configurations at the personal level:

Bet: soon replaced
Stack wealth before skills depreciate. If reality is amplification instead of displacement, you may miss history's best skill-building window.
Bet: amplifies people
Build AI-complementary skills now—agency, taste, judgment. He stands here.

Floor vs ceiling: where saved time goes

He frames personal strategy with a pair of words:

Floor
What AI can do alone. The floor will rise—that is the line industry narratives blast daily.
Ceiling
What you can take on after AI amplifies you—ambitious projects you could not hold before. The ceiling does not rise on its own; you have to push it.

His move: when AI clearly lifts productivity, reinvest the saved time in long-term growth—new skills and workflows that complement AI. He spends roughly 10 hours a week only on learning and trying new processes.

A blunt self-check

"If I finish a day completely unexhausted, I did it wrong—I offloaded too much to AI and traded long-term growth for short-term output."

Three-legged stool: productivity · growth · control

Faster delivery with AI is not the only goal. Three legs have to stand at once:

ProductivityShip the work, faster
+
GrowthSkills and workflow compound
+
ControlHumans still hold the wheel

Push only productivity and starve growth, and a rising floor flattens you. Chase only growth and ignore delivery, and reality ends you. Have both but surrender control, and long-term you become a button-pusher.

Two heuristics for keeping control

① Resist the black-box lure
Vendors want you to treat the agent as a black box: one prompt, it finishes alone. He calls that a trap—dangerous, and a slow handoff of control.
② Watch the dependence spiral
The tasks you are weakest at are the ones you most want to dump on AI—learning is hard. Residual skill keeps atrophying. Better long-term order: master it yourself, then let AI amplify.
Back to the crane

Machines do the cognitive heavy work; people stay in the cab. The job becomes operating, understanding, and controlling the machine—not hauling every brick by hand. Personal adaptation means not climbing out of the cab to become just another brick on the schedule.

Crane-operator metaphor
The job is redefined as operating and controlling the machine. Source: talk slides
10 Vision

Closing vision: human–machine co-superintelligence

In one sense, economically transformative AI has already started: not when some AGI switch flips, but as slow variables—reliability, integration, tacit knowledge, regulation—rewrite work. He rejects geopolitics reduced to "whoever hits a capability milestone first takes all the economic returns."

On superintelligence he stresses: tasks often have ceilings; human intelligence leans hard on learning and tools, and AI is another tool—so the contest looks more like AI-augmented people vs AI acting alone. If we default to a future where AI owns companies and decides hiring and firing, then lean only on alignment as a backstop, that safety posture "opposes safety more than it supports it."

Co-superintelligence
Vision: co-superintelligence. Source: talk slides

He likens computers to "bicycles for the mind" and AI to "cranes for the mind"—lifting human potential to heights once unimaginable. The learning curve is steep, like a treadmill that never stops. He still treats co-superintelligence as a fight worth fighting: not abandoning work, but redefining it as a higher-ceiling dance with AI.

Takeaways
Talk takeaways slide. Source: talk slides
The capability floor rises on its own; you have to push the ceiling. Adaptation is not dumping all work on AI—it is reinvesting saved time in complementary skills, and staying in the control seat. Based on Arvind Narayanan · ICML 2026 keynote
Based on Arvind Narayanan's ICML 2026 keynote "What will be left for us to work on?" and his illustrated write-up on AI as Normal Technology (2026-07-14). Figures such as reliability +5–10pp, ~24-month window, execute ~1/3 of hours, and ~10,000× software employment growth are research/historical claims reported in the talk; SAGE metrics are the lab's own composite. Annotated slides: cs.princeton.edu/~arvindn/talks/icml-2026-annotated-slides/ · Source: normaltech.ai