Context Advantage, Not Taste

Sources#

• Thread by @AndrewYNg

Summary#

In a June 2026 letter otherwise devoted to a loop taxonomy, Andrew Ng makes an aside that quietly reframes the wiki's most-asked question:

"Many people describe this human contribution as 'taste,' but I prefer to think of it as humans having a context advantage, since that gives us a clearer path to helping AI systems get better. This also speaks to why this step can't be automated: so long as the human knows something the AI does not, human-in-the-loop is needed to inject that knowledge into the system."

The wiki has spent a whole page asking whether taste is a genuine ceiling or "just another AI capability that AI systems fail at for a time, then get good at." Ng's answer is: neither — it's a category error. What people call taste is not a capability the human has and the model lacks; it is knowledge the human has and the model hasn't been given. "We know a lot more than the AI system about the users and the context the product has to operate in."

The reframe is not cosmetic. It changes what kind of thing the human role is, and therefore what would end it. (practitioner-opinion — Ng offers no measurement, and states the preference as a preference.)

Why the reframe is load-bearing#

Three consequences follow immediately, and each one flips the sign of a claim elsewhere in this wiki.

1. It makes the human role falsifiable. "Taste" is unfalsifiable by construction — you cannot check whether a model has it, only whether experts like its output. A context advantage has a truth condition: does the human hold information the model doesn't? You can enumerate that information, and you can watch the list shrink.

2. It makes the role a gap, not a moat. Ng's own justification for preferring the frame is instrumental: it "gives us a clearer path to helping AI systems get better." A moat is something you defend; a gap is something you close. Read literally, the sentence "so long as the human knows something the AI does not, human-in-the-loop is needed" states the human's necessity and its expiry condition in the same breath. It is a strictly weaker claim about human durability than the taste framing it replaces, and Ng seems to intend it that way.

3. It relocates the work from cultivation to transfer. If the residue is taste, the response is to develop taste. If the residue is a context asymmetry, the response is elicitation and transfer — get the knowledge out of the human's head and into the system. Which is precisely what Thariq Shihipar's field guide, published four days later and citing nothing of Ng's, is a manual for.

The convergence: unknown knowns are the context advantage#

Thariq's four-quadrant breakdown names a cell he calls unknown knowns: "what's so obvious I'd never write it down, but would recognize it if I saw it."

That is the context advantage seen from inside the human's head. It is invisible to its holder for the same reason it is invisible to the model — nobody writes down the obvious. Ng says the human's value is knowing things the model doesn't; Thariq says the hard part is that the human doesn't know which things those are. Put together:

• Ng supplies the criterion. The human is needed exactly as long as the asymmetry exists.
• Thariq supplies the protocol. Blindspot passes, interviews, prototypes, and references are all instruments for pumping information across the asymmetry — before, during, and after the work.

Two practitioners, one week apart, no cross-citation, describing the same object from opposite ends. This is the strongest cross-source convergence in the corpus on what the human is actually for.

The uncomfortable implication#

If the human's necessity is an information asymmetry, then every artifact that transfers context narrows it. CLAUDE.md and AGENTS.md, skills, memory files, codebase indexes, production-sourced evals — the entire externalized-context stack exists to move what the human knows into where the model can read it. Under the taste framing these tools amplify the human. Under Ng's framing they spend the human's advantage, deliberately, one file at a time.

This is not an argument against writing them. It is an observation that the wiki's two most-recommended practices — externalize your context, and treat human judgment as the durable residue — are in tension, and Ng's frame is what makes the tension visible. The practices are consistent only if the asymmetry regenerates faster than it is transferred: new users, new markets, new products, new constraints. Whether it does is an empirical question nobody in the corpus has posed, let alone answered.

Where the reframe is too clean#

Ng's frame explains the deployment asymmetry well and the generative one badly.

• Deployment asymmetry (Ng is right). "We know a lot more about the users and the context the product has to operate in." This is private information. It is transferable in principle, and it is exactly what Anthropic's 400K-session study measures: domain understanding of the problem — not coding skill — predicts who gets quality work out of an agent. Anthropic reads a decrease in the returns to expertise over time as evidence that "models are starting to supply the essential judgment users currently bring." Under Ng's frame, that is not a mystery: it is the context gap closing, and the returns-to-expertise curve is the instrument for watching it close.
• Generative asymmetry (Ng doesn't address it). DeepMind's argument is that AI may be bounded by human conceptual frameworks — not lacking a fact, but unable to originate the concept in which the fact would be stated. Ditto Boden level-3 creativity: creating a new conceptual space is not an information deficit that better context transfer repairs. If a human's contribution is that they can invent a frame the model cannot, "knows something the AI does not" is technically true and completely misleading.

So the honest statement is that Ng dissolves the product-work version of the taste question and leaves the research-frontier version standing. Which is consistent with the domain he's writing from: 0-to-1 consumer products, where the missing knowledge really is "what my daughter wants from a typing app," not a new conceptual space.

Against it: taste as something other than information#

The strongest counter is that some of what "taste" names is not knowledge at all but discrimination under uncertainty — a reliable preference ordering over options none of which you can articulate a criterion for. Thariq's color-grading episode is the crisp case: he had the information (Claude could generate variations) and still could not proceed, because he couldn't grade the options. His fix was to acquire the criterion — which is Ng's frame, one level up: the missing thing was information about what good looks like, and it was obtainable.

That the hardest example in the corpus resolves in Ng's favor is a point for the reframe. Design is where it will be tested: if design taste is a context gap, it closes; if it is discrimination without a statable criterion, it doesn't.

Connections#

• Research Taste as the Human Bottleneck — the page this reframes. Its central open question ("is taste a genuine ceiling or the next jagged valley?") presupposes taste is a capability; Ng argues it is an asymmetry, which makes it neither ceiling nor valley but a gap that closes as context transfers
• Unknowns as the Agentic Bottleneck — the extraction protocol for the asymmetry; Thariq's unknown knowns are this concept viewed from inside the human's head
• The Three Loops of AI-Native Building — the context advantage is why the human occupies the middle loop: they are the transmission between the loop that knows the users and the loop that writes the code
• Returns to Expertise in Agentic Coding — the instrument. If the human role is a closable context gap, the measured decline in expertise premium is the gap closing, tracked in usage data
• Outsource Your Thinking, Not Your Understanding — Karpathy's residue is understanding, which is closer to Ng's "context" than to "taste"; both locate the human in what they know rather than in what they can appreciate
• Agent Context Files — the transfer mechanism, and the uncomfortable implication: every skill file you write spends a little of your own advantage
• The Abstraction Barrier — the limit case Ng's frame doesn't reach: being bounded by human conceptual frameworks is not a missing fact
• Transformative Creativity — Boden level-3 as the generative asymmetry that context transfer cannot repair
• Why AI Lags at Design — the test case: design taste is either a context gap (closes) or criterion-less discrimination (doesn't)
• Jagged Intelligence (Ghosts, Not Animals) — the framing Ng displaces: "a capability AI fails at then masters" assumes taste is a capability at all
• Implementation Abundance Inverts Product Work — Ambrosino names curation/taste as the new bottleneck without asking what taste is; Ng supplies the answer that makes the bottleneck perishable
• Engineer PM Convergence — the practical consequence: if the convergent skill is proximity to the user rather than taste, "hire for taste" is a perishable strategy
• Production-Sourced Evaluation — context transfer as infrastructure: sourcing evals from real usage moves the human's private knowledge of users into where the model can read it
• Andrew Ng — author of the reframe

Open questions#

• Does the asymmetry regenerate faster than it transfers? The whole human role, under this frame, rests on the answer. Nobody in the corpus has posed it.
• Ng prefers the frame because it "gives us a clearer path to helping AI systems get better." That is a reason to adopt the frame, not evidence that it's true. What would distinguish a context asymmetry from a capability gap empirically? (Returns to Expertise in Agentic Coding is the closest thing to an instrument.)
• If the human's contribution is context injection, is the human replaceable by better context plumbing — memory, retrieval, continuous production telemetry — rather than by a better model? That would put the expiry of human-in-the-loop on the infrastructure roadmap, not the scaling curve.
• Ng writes from 0-to-1 consumer products. Does the frame survive contact with domains where the missing thing is a concept rather than a fact?

Sources#

• Thread by @AndrewYNg — Andrew Ng, The Batch, published 2026-06-30 (practitioner-opinion); the context-advantage passage sits inside the developer-feedback-loop section
• A Field Guide to Fable: Finding Your Unknowns — Thariq Shihipar, 2026-07-04 (practitioner-opinion); unknown knowns as the same object, and the color-grading episode as the hard case